search

rorysenpai / jaikuengine

Automatically exported from code.google.com/p/jaikuengine
Apache License 2.0
0 stars 0 forks source link

Feeds do not have proper caching headers, etags #109

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
To reproduce:

curl -v http://bslatkin.jaiku.com/atom 1>/dev/null
* About to connect() to bslatkin.jaiku.com port 80 (#0)
*   Trying 74.125.53.141... connected
* Connected to bslatkin.jaiku.com (74.125.53.141) port 80 (#0)
> GET /atom HTTP/1.1
> User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3
OpenSSL/0.9.7l zlib/1.2.3
> Host: bslatkin.jaiku.com
> Accept: */*
> 
< HTTP/1.1 200 OK
< Expires: Fri, 01 Jan 1990 00:00:00 GMT
< Content-type: application/atom+xml; charset=utf-8
< Pragma: no-cache
< Cache-control: no-cache, must-revalidate
< Date: Wed, 06 May 2009 18:16:37 GMT
< Server: Google Frontend
< Transfer-Encoding: chunked

What is the expected output? What do you see instead?

Last-modified and ETag headers, so polling clients can cache the feed and
do if-modified-since and if-none-match polling in the future. This will
reduce the overall bandwidth of polling Jaiku feeds.

Original issue reported on code.google.com by bslatkin on 6 May 2009 at 6:19

GoogleCodeExporter commented 8 years ago 
patches welcome :)

Original comment by andyster on 19 May 2009 at 1:30