[Registry-dev] Support for If-Modified-Since header

Sanjiva Weerawarana sanjiva at wso2.com
Thu Jan 3 08:44:32 PST 2008


Can you validate that its working properly with the browser? You can stick 
tcpmon in between and watch the messages .. the browser should be putting 
that header for the resource accesses.

Sanjiva.

Chathura C. Ekanayake wrote:
> 
> I have implemented the support for "If-Modified-Since" header in the 
> Registry.
> Now the registry servlet adds the "Last-Modified" header to all resource 
> content responses.
> Then the subsequent requests from clients (web browsers, APP client) may 
> include
> the "If-Modified-Since" header with the last modified value of the 
> previous response.
> 
> If the date/time specified in the "If-Modified-Since" header is greater 
> than or equal to the last modified date/time of the resource,
> Registry responds with a "304 Not Modified " response.
> 
> If a client does not support caching, it can simply avoid adding the 
> "If-Modified-Since" header, in which case
> the resource content is always returned in the response.
> 
> Thanks,
> Chathura
> 
> 
> _______________________________________________
> Registry-dev mailing list
> Registry-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
> 

-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
email: sanjiva at wso2.com; cell: +1 650 265 8311 | +94 77 787 6880

"Oxygenating the Web Service Platform."



More information about the Registry-dev mailing list