$config->requestUrl() method

Current unsanitized request URL

  • This is an alternative to $input->url() that’s available prior to API ready state.
  • Useful if you need to know request URL from /site/config.php or other boot file.
  • Returned value does not include query string, if present.
  • Returned value includes installation subdirectory, if present.

Available since version 3.0.175.

Example

if($config->requestUrl() === '/products/2021/') {
  // current request URL is exactly “/products/2021/”
}
if($config->requestUrl('/products/2021/')) {
  // current request matches “/products/2021/” somewhere in URL
}
if($config->requestUrl([ 'foo', 'bar', 'baz' ])) {
  // current request has one or more of 'foo', 'bar', 'baz' in the URL
}

Usage

// basic usage
$string = $config->requestUrl();

// usage with all arguments
$string = $config->requestUrl($match = '', string $get = '');

Arguments

NameType(s)Description
match (optional)string, array

Optionally return URL only if some part matches given string(s) (default='')

get (optional)string

Specify 'path' to get and/or match path, 'query' to get and/or match query string, or omit for URL (default='')

Return value

string

Returns URL string or blank string if $match argument used and doesn’t match.


$config methods and properties

API reference based on ProcessWire core version 3.0.236

Latest news

  • ProcessWire Weekly #544
    In the 150th issue of ProcessWire Weekly we'll check out brand-new third party module called Inputfield Dependency Helper, share some recent highlights from the support forum, and more. Read on!
    Weekly.pw / 12 October 2024
  • Custom Fields Module
    This week we look at a new ProFields module named Custom Fields. This module provides a way to rapidly build out ProcessWire fields that contain any number of subfields/properties within them.
    Blog / 30 August 2024
  • Subscribe to weekly ProcessWire news

“I am currently managing a ProcessWire site with 2 million+ pages. It’s admirably fast, and much, much faster than any other CMS we tested.” —Nickie, Web developer