I validated it using firefox and tcpmon and it works exactly as
expected. When the browser sends the first GET request, it returns the
resource content. For subsequent requests, Registry sends the 304
response (if the modified date is valid) and the browser gives the
resource content from the cache.
Thanks,
Chathura
Sanjiva Weerawarana wrote:
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
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
