Standards Compliance in Squid
Synopsis
Squid behaviour is governed by a great many International standards and requirements. Below is a list of the standards to which Squid is expected to obey and an indication of whether we believe it does.
- This list was updated 2021-12-14. Details are believed to be accurate for the current release 5.3 or later.
this list is known to be incomplete. If you are aware of anything important which has been omitted please report it as a website bug.
Formal Certifications
At this point there are none on record. We are looking for information and possibly sponsorship to obtain any certifications which are required for use in your network.
IEFT RFC standards
RFC |
Name |
Status |
||
FILE TRANSFER PROTOCOL (FTP) |
|
|||
DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION |
|
client only |
||
A Simple Network Management Protocol (SNMP) |
|
|
||
Identification Protocol (IDENT) |
|
note bug 2853 |
||
The Internet Gopher Protocol |
|
client and gateway to HTTP |
||
Structure of Management Information |
|
|||
Protocol Operations |
|
|||
Hypertext Transfer Protocol -- HTTP/1.0 |
|
|||
A Trivial Convention for using HTTP in URN Resolution |
|
|||
Clarifications to the DNS Specification |
|
|||
Internet Cache Protocol (ICP), version 2 |
|
|||
Application of Internet Cache Protocol (ICP), version 2 |
|
|||
Simple Hit-Metering and Usage-Limiting for HTTP |
|
|||
Transparent Content Negotiation in HTTP |
|
|||
HTTP Remote Variant Selection Algorithm -- RVSA/1.0 |
|
|||
The Safe Response Header Field |
|
Specifications for this feature are deprecated. |
||
FTP Extensions for IPv6 and NATs |
|
since Squid-3.1 |
||
HTTP Extensions for Distributed Authoring -- WEBDAV |
|
since Squid-3.1 |
||
Traffic Flow Measurement: Architecture |
|
|||
Hyper Text Caching Protocol (HTCP/0.0) |
|
|||
An HTTP Extension Framework |
|
|||
Upgrading to TLS Within HTTP/1.1 |
|
|||
HTTP Over TLS |
|
|||
Use of HTTP State Management |
|
|||
HTTP State Management Mechanism |
|
|||
3205 (BCP 56) |
On the use of HTTP as a Substrate |
|
||
Indicating Resolver Support of DNSSEC |
|
|
||
DNSSEC and IPv6 A6 aware server/resolver message size requirements |
|
|||
Versioning Extensions to WebDAV |
|
since Squid-3.1 |
||
Hypertext Transfer Protocol (HTTP) Digest Authentication |
|
|||
Basic Socket Interface Extensions for IPv6 |
|
|||
Internet Content Adaptation Protocol (ICAP) |
|
client only, PRECACHE vectors only |
||
DNS Extensions to Support IP Version 6 |
|
|||
Web Distributed Authoring and Versioning (WebDAV)<BR>>Access Control Protocol |
|
since Squid-3.1 |
||
The Common Gateway Interface (CGI) Version 1.1 |
|
cachemgr.cgi |
||
Uniform Resource Identifier (URI): Generic Syntax |
|
since Squid-4.12. still uses rc1738 encoder on some URI segments and helper protocol. Merge Request 335 |
||
Textual Conventions for Internet Network Addresses |
|
|||
The gopher URI Scheme |
|
|||
The telnet URI Scheme |
|
|||
IP Version 6 Addressing Architecture |
|
|||
SPNEGO-based Kerberos and NTLM HTTP Authentication |
|
|||
HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) |
|
|||
Use of the Content-Disposition Header Field in the |
|
|||
6540 (BCP 177) |
IPv6 Support Required for All IP-Capable Nodes |
|
||
URI Template |
|
|||
Additional HTTP Status Codes |
|
|||
Multicast DNS |
|
client only |
||
The OAuth 2.0 Authorization Framework: Bearer Token Usage |
|
Merge Request 30 |
||
Representing IPv6 Zone Identifiers in |
|
|||
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing |
almost |
see Features/HTTP11 |
||
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
almost |
see Features/HTTP11 |
||
Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests |
almost |
see Features/HTTP11 |
||
Hypertext Transfer Protocol (HTTP/1.1): Range Requests |
|
conditional, see Features/HTTP11 |
||
Hypertext Transfer Protocol (HTTP/1.1): Caching |
|
conditional, see Features/HTTP11 |
||
Hypertext Transfer Protocol (HTTP/1.1): Authentication |
|
|||
Initial Hypertext Transfer Protocol (HTTP) |
almost |
missing support for Bearer and OAuth schemes |
||
Initial Hypertext Transfer Protocol (HTTP) Method Registrations |
|
|||
Forwarded HTTP Extension |
|
Merges Request 55 |
||
Prefer HTTP Extension |
|
conditional; proxy MUST relay unless listed in Connection header. |
||
The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect) |
|
|||
Hypertext Transfer Protocol Version 2 (HTTP/2) |
|
|
||
HPACK: Header Compression for HTTP/2 |
|
see Features/HTTP2 and Merge Request 893 |
||
Guidelines and Registration Procedures for URI Schemes |
|
Missing prohibition of example: URI scheme |
||
HTTP Authentication-Info and Proxy-Authentication-Info |
|
|||
HTTP Digest Access Authentication |
|
Missing support for several Digest features |
||
The 'Basic' HTTP Authentication Scheme |
|
missing new charset support. |
||
The ALPN HTTP Header Field |
|
|||
Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding |
|
|||
An HTTP Status Code to Report Legal Obstacles |
|
|||
HTTP Alternative Services |
|
|||
Specification for DNS over Transport Layer Security (TLS) |
|
|||
Opportunistic Security for HTTP/2 |
|
|||
Indicating Character Encoding and Language for HTTP Header Field Parameters |
|
|||
Encrypted Content-Encoding for HTTP |
|
|||
HTTP Immutable Responses |
|
partial. see bug 4774 |
||
An HTTP Status Code for Indicating Hints |
|
|||
The ORIGIN HTTP/2 Frame |
|
|||
Bootstrapping WebSockets with HTTP/2 |
|
|||
Using Early Data in HTTP |
|
Merge Request 873 |
||
Loop Detection in Content Delivery Networks (CDNs) |
|
from Squid-5. |
||
Well-Known Uniform Resource Identifiers (URIs) |
|
|||
HTTP Random Access and Live Content |
|
|||
Using TLS 1.3 with HTTP/2 |
|
|||
Structured Field Values for HTTP |
|
|||
HTTP Client Hints |
|
|||
Version-Independent Properties of QUIC |
|
Merge Request 919 |
||
QUIC: A UDP-Based Multiplexed and Secure Transport |
|
Merge Request 919 |
||
Using TLS to Secure QUIC |
|
|||
QUIC Loss Detection and Congestion Control |
|
IETF Drafts
https://datatracker.ietf.org/doc/html/draft-forster-wrec-wccp-v1 |
WCCP 1.0 |
|
|
https://datatracker.ietf.org/doc/html/draft-wilson-wrec-wccp-v2 |
WCCP 2.0 |
almost |
|
https://datatracker.ietf.org/doc/html/draft-param-wccp-v2rev1-01 |
WCCP 2.0 rev 1 |
|
|
Microsoft CARP peering algorithm |
|
||
https://datatracker.ietf.org/doc/html/draft-ietf-radext-digest-auth |
RADIUS Extension for Digest Authentication |
|
|
https://datatracker.ietf.org/doc/html/draft-kazuho-early-hints-status-code |
103 Early Hints Status Code |
|
|
https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-proxy-status |
The Proxy-Status HTTP Response Header Field |
|
|
https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-targeted-cache-control |
Targeted HTTP Cache Control |
|
|
HTTP/3 |
|
ISO standards
ISO-8859-1 |
Latin alphabet No. 1 |
|
Non-standard Protocols
The PROXY protocol, Versions 1 & 2 |
|