HTTP/1.1 demos

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> <HTML> <HEAD>  <TITLE>HTTP/1.1 demos</TITLE>  <STYLE TYPE="text/css"> .right { float: right; margin-bottom: 60; } .left { float: left; } </STYLE> </HEAD> <BODY BGCOLOR="white"> <A HREF=".."><IMG CLASS="left" SRC="/icons/jigsaw" ALT="Jigsaw" BORDER="0" WIDTH="212" HEIGHT="49"></A> <IMG CLASS="right" SRC="/icons/jigpower.gif" WIDTH="94" HEIGHT="52" ALT="Jigsaw Powered !" BORDER="0" ALIGN="Right"> <H1> A set of HTTP/1.1 features </H1> <HR> DISCLAIMER: Jigsaw tries to implement all features of HTTP/1.1, it has not however reached a Refernce Implementation status of any sort with regard to HTTP/1.1. This "test suite" has been established temporarily, in particular: <UL> <LI> We do not guarantee protocol conformance on any of the tests, <LI> This service must not be refered to as a "conforming testing" <LI> This service must not be mentioned in any commercial like situation </UL> <HR> You're looking for a server implementing a specific HTTP/1.1 feature ? If that feature is not in the included list below, send mail to <A HREF="mailto:jigsaw@w3.org">jigsaw@w3.org</A>. <TABLE BORDER CELLPADDING="2"> <TR> <TD><A HREF="ChunkedScript">Chunk Encoding</A></TD> <TD>Jigsaw will chunk encode any stream that needs to be chunk encoded automatically, when possible. This link points to a CGI script, whose output will be chunk encoded if you're using an HTTP/1.1 client.</TD> </TR> <TR> <TD><A HREF="TE/foo.txt">TE</A></TD> <TD>Jigsaw will serve you this text file, according to the transfer-encoding present in the request. It can serve the resource using gzip or deflate compression scheme. </TR> <TR> <TD><A HREF="TE/bar.txt">TE (bis)</A></TD> <TD>Jigsaw will serve you this text file, according to the transfer-encoding present in the request. It can serve the resource using gzip or deflate compression scheme, the data comes from another resource, so a Content-Location: header is added. </TR> <TR> <TD><A HREF="connection.html">Connection</A></TD> <TD>The Connection header is used in HTTP/1.1 to mark a header as "hop-by-hop" only. Proxies, for example, should remove header listed in Connection.</TD> </TR> <TR> <TD><A HREF="cc.html">Cache-Control </A> (max-age)</TD> <TD>Jigsaw will always emit appropriate Cache-Control info. This link points to a page whose cache control max-age value has been set to 120 seconds.</TD> </TR> <TR> <TD><A HREF="cc-private.html">Cache-Control </A>(private)</TD> <TD>This links points to a page that will be served with a private cache control directive.</TD> </TR> <TR> <TD><A HREF="cc-proxy-revalidate.html">Cache-Control </A>(proxy-revalidate)</TD> <TD>This links point to a page that will be served with a proxy-revalidate cache control directive.</TD> </TR> <TR> <TD><A HREF="cc-nocache.html">Cache-Control</A> (no-cache)</TD> <TD>This links points to a page which has  a fake Set-Cookie header, and which include a Cache-Control: no-cache="Set-Cookie" header. Meant to test proxies.</TD> </TR> <TR> <TD><A HREF="h-content-md5.html">Content-MD5</A></TD> <TD>This links points to a resource served with its MD5 digest. It gives an indication that the integrity of the entity body has been respected. Note that it only for accidental modification or errors, not to check for malicious attacks. In this example, the value should be: Content-Md5: 0TMnkhCZtrIjdTtJk6x3+Q== </TD> </TR> <TR> <TD><A HREF="h-retry-after.html">Retry-After</A> (delay)</TD> <TD>This link points to something which can be unavailable, depending on the date and time. If it is not available, it will give the delay of expected unavailability.</TD> </TR> <TR> <TD><A HREF="h-retry-after-date.html">Retry-After</A> (date)</TD> <TD>This link points to something which can be unavailable, depending on the date and time. If it is not available, it will give the date of expected availability.</TD> </TR> <TR> <TD><A HREF="neg">300 Multiple Choices</A></TD> <TD>This link points to a resource which can give two resources. One for text/html, one for text/plain. If you have the same quality level for both, the server will return a 300 Multiple Choices along with a list of available variants. </TD> </TR> <TR> <TD><A HREF="negbad">406 Not Acceptable</A></TD> <TD>This link points to a resource which cannot be served, according to the Accept header sent. The server will return a 406 Not Acceptable to notify the failure of the request. </TD> </TR> <TR> <TD><A HREF="400/toolong/">414 Request-URI Too Long</A></TD> <TD>This link points to a resource which cannot be served, as the URI to reach it will be too long. The server will return a 414 Request-URI Too Long to notify the failure of the request. </TD> </TR> <TR> <TD><A HREF="300/">Redirect test page</A></TD> <TD>This link point to a page demonstrating some redirect response codes. </TD> </TR> <TR> <TD><A HREF="Basic/">Basic Authentication test</A></TD> <TD>This link point to a protected resource, to access it, the user is "guest" and the password is also "guest". </TD> </TR> <TR> <TD><A HREF="Digest/">Digest Authentication test</A></TD> <TD>This link point to a protected resource, to access it, the user is "guest" and the password is also "guest". This page is protected using <A HREF="ftp://ftp.ietf.org/internet-drafts/draft-ietf-http-authentication-03.txt">Digest Authentication</A>. </TD> </TR> <TR> <TD><A HREF="CL/">Content-Location test</A></TD> <TD>This link point to resource whose content is in another directory. The computation of the base URI of this document has to be done according to the <code>Content-Location</code> header sent by the server. </TD> </TR> </TABLE> </BODY></HTML>

CINXE.COM

HTTP/1.1 demos