Some web servers enable HTTP compression and conditional GET to reduce bandwidth usage with browsers that support these technologies. Use this tool to test whether a webpage supports HTTP compression and conditional GET.
Type the full URL of the webpage to test (including the "http://" protocol prefix): Example: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
Click Test this URL to see the results below.
A summary of what the tested web server reported is displayed beneath the button, including the support status of both HTTP compression and conditional GET.
If conditional GET is enabled, you can further test this feature.
To determine whether the webpage tested was changed since a specified date, select a comparison date in the calendar, and then run the test again. This queries the If-Modified-Since HTTP request-header field on the web server.
Select a date:
If the results for the HTTP status code show 304 Not Modified, the page has not been modified since the date selected in the calendar. However, if the HTTP status code in the results show 200 OK, the page was modified since the date selected.
Some web servers return HTTP header ETag values. ETags are GUIDs based on the If-None-Match HTTP request-header field on the web server. If the webpage tested returned an ETag value GUID, you can also test that value to determine whether the ETag GUID returned for today is different than from another date, indicating the page has changed between the tested date and today.
To determine whether a webpage was modified since a specified date using an ETag value, select a comparison date, and then type or paste the ETag value:
If the HTTP status code in the results show 304 Not Modified, the page has not been modified since the date selected on the calendar. If the status code returned is 200 OK, the page has been changed since the comparison date.