wppaste
WordPress

iis7_supports_permalinks(): bool

Since
2.8.0
Source
wp-includes/functions.php:6240
Checks if IIS 7+ supports pretty permalinks.

Compatibility

WordPress
since 2.8.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Return value

bool
Whether IIS7 supports permalinks.

Performance profile

How much work a call to iis7_supports_permalinks() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class
Trivial

Touches nothing outside its own arguments.

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
8–15

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 15.

Plugin surface
1 hook

Third-party callbacks on 'iis7_supports_permalinks' run inside this call, and their cost is not bounded by anything here.

Called by
4

4 places in core call this, so the cost is paid more often than your own code shows.

What it touches

  • hookthird-party callbacksapply_filters()called directly

What one call costs · 1 distinct outcome

One number would be a lie: the work depends on which branch runs. These are every distinct cost iis7_supports_permalinks() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always8–15apply_filters()

Across PHP versions

PHPCompiledExecutedBranchesNotes
8.6-dev158–153
8.5158–153
8.4158–1533 fewer instructions than PHP 8.3
8.3188–183
8.2188–183
8.1188–183
7.4188–183

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Hooks and filters fired · 1

One hook fires while iis7_supports_permalinks() runs, in this order:

  1. apply_filters( iis7_supports_permalinks )filterline 6264 (+24 into the body)

    Filters whether IIS 7+ supports pretty permalinks.

Uses · 1

  • apply_filters()Calls the callback functions that have been added to a filter hook.

Used by · 4

Source code

function iis7_supports_permalinks() {	global $is_iis7; 	$supports_permalinks = false;	if ( $is_iis7 ) {		/* First we check if the DOMDocument class exists. If it does not exist, then we cannot		 * easily update the xml configuration file, hence we just bail out and tell user that		 * pretty permalinks cannot be used.		 *		 * Next we check if the URL Rewrite Module 1.1 is loaded and enabled for the website. When		 * URL Rewrite 1.1 is loaded it always sets a server variable called 'IIS_UrlRewriteModule'.		 * Lastly we make sure that PHP is running via FastCGI. This is important because if it runs		 * via ISAPI then pretty permalinks will not work.		 */		$supports_permalinks = class_exists( 'DOMDocument', false ) && isset( $_SERVER['IIS_UrlRewriteModule'] ) && ( 'cgi-fcgi' === PHP_SAPI );	} 	/**	 * Filters whether IIS 7+ supports pretty permalinks.	 *	 * @since 2.8.0	 *	 * @param bool $supports_permalinks Whether IIS7 supports permalinks. Default false.	 */	return apply_filters( 'iis7_supports_permalinks', $supports_permalinks );}

Changelog

Introduced in 2.8.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data
Generated from the wordpress-develop 7.0.4 tag, from src/wp-includes/functions.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.