uri.thephpleague.com

• charset: utf-8
• equiv: X-UA-Compatible content: IE=edge
• name: viewport content: width=device-width, initial-scale=1
• name: theme-color content: #386FFF
• name: description content:
• name: keywords content: URI, URL, URN, RFC3986, RFC3987, RFC6570, RFC2141, RFC8141, WHATWG URL, URI Template, Fragment Text Directives, RFC, PHP URI Polyfill, URI modifiers, URI components, IDNA, Query String
• name: docsearch:version content:
• name: twitter:card content: summary_large_image
• name: twitter:site content: @thephpleague
• name: twitter:title content:
• name: twitter:description content:
• name: twitter:creator content: @nyamsprod
• name: twitter:image:src content: https://uri.thephpleague.com/assets/img/uri_large_logo.png
• itemprop: name content:
• itemprop: description content:
• itemprop: image content: https://uri.thephpleague.com/assets/img/uri_large_logo.png
• property: og:title content:
• property: og:description content:
• property: og:image content: https://uri.thephpleague.com/assets/img/uri_large_logo.png

• http://uri.thephpleague.com/interfaces/7.0/
• http://uri.thephpleague.com/uri/7.0/
• http://uri.thephpleague.com/components/7.0/
• http://uri.thephpleague.com/polyfill/7.0/
• https://uri.thephpleague.com/

• SOURCE CODE
• RFC 3986
• RFC 8141
• WHATWG URL Living Standard
• PSR-7
• PSR-17
• Sponsor its development
• https://csv.thephpleague.com/
• https://period.thephpleague.com/
• The League of
• Package created and maintained by
• Brand and site design by
• The MIT License (MIT)

            Domain Name: THEPHPLEAGUE.COM
Registrar: Key-Systems GmbH
Domain Status: client transfer prohibited
Creation Date: 2013-07-24T13:52:20Z
Registry Expiry Date: 2026-07-24T13:52:20Z
Updated Date: 2025-11-28T03:32:27Z
Name Server: DIVA.NS.CLOUDFLARE.COM
Name Server: HUGH.NS.CLOUDFLARE.COM
REGISTRAR Contact: Key-Systems GmbH
>>> Last update of RDAP database: 2026-01-26T22:12:04Z         

			# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a content-signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a content-signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a content signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via content signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.
        

Techniczne SEO

SEO na stronie

Treść i UX