Squid configuration directive uri_whitespace
Available in: v7 v6 v5 v4 3.5 3.4 3.3 3.2 2.7 3.1 3.0 2.6
For older versions than v4 see the linked pages above
Configuration Details:
Option Name: | uri_whitespace |
---|---|
Replaces: | |
Requires: | |
Default Value: | uri_whitespace strip |
Suggested Config: |
|
What to do with requests that have whitespace characters in the URI. Options: strip: The whitespace characters are stripped out of the URL. This is the behavior recommended by RFC2396 and RFC3986 for tolerant handling of generic URI. NOTE: This is one difference between generic URI and HTTP URLs. deny: The request is denied. The user receives an "Invalid Request" message. This is the behaviour recommended by RFC2616 for safe handling of HTTP request URL. allow: The request is allowed and the URI is not changed. The whitespace characters remain in the URI. Note the whitespace is passed to redirector processes if they are in use. Note this may be considered a violation of RFC2616 request parsing where whitespace is prohibited in the URL field. encode: The request is allowed and the whitespace characters are encoded according to RFC1738. chop: The request is allowed and the URI is chopped at the first whitespace. NOTE the current Squid implementation of encode and chop violates RFC2616 by not using a 301 redirect after altering the URL. |
|
Introduction
- About Squid
- Why Squid?
- Squid Developers
- How to Donate
- How to Help Out
- Getting Squid
- Squid Source Packages
- Squid Deployment Case-Studies
- Squid Software Foundation
Documentation
- Quick Setup
- Configuration:
- FAQ and Wiki
- Guide Books:
- Non-English
- More...
Support
- Security Advisories
- Bugzilla Database
- Mailing lists
- Contacting us
- Commercial services
- Project Sponsors
- Squid-based products
Miscellaneous
- Developer Resources
- Related Writings
- Related Software:
- Squid Artwork
Web Site Translations
Mirrors
- Website:
- gr il pl ... full list
- FTP Package Archive