Squid configuration directive broken_posts
Available in: 3.3 3.2 3.1 2.7 3.HEAD 2.HEAD 3.0 2.6
Configuration Details:
Option Name: | broken_posts |
---|---|
Replaces: | |
Requires: | --enable-http-violations |
Default Value: | none |
Suggested Config: |
|
A list of ACL elements which, if matched, causes Squid to send an extra CRLF pair after the body of a PUT/POST request. Some HTTP servers has broken implementations of PUT/POST, and rely on an extra CRLF pair sent by some WWW clients. Quote from RFC2616 section 4.1 on this matter: Note: certain buggy HTTP/1.0 client implementations generate an extra CRLF's after a POST request. To restate what is explicitly forbidden by the BNF, an HTTP/1.1 client must not preface or follow a request with an extra CRLF. This clause only supports fast acl types. See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. Example: acl buggy_server url_regex ^http://.... broken_posts allow buggy_server |
|
Search
Introduction
- About Squid
- Why Squid?
- Squid Developers
- How to Help Out or Donate
- Getting Squid
- Squid Source Packages
- Squid Deployment Case-Studies
- Squid Software Foundation
Documentation
- 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