chesterpolo / mongoose

Automatically exported from code.google.com/p/mongoose
MIT License
0 stars 0 forks source link

Caching does not work correct #149

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Watch the http traffic with wireshark
2. Open a image (png) in the browser
3. Reload the image

What is the expected output? What do you see instead?
My browser sends this in the http header:
Cache-Control: max-age=0\r\n
If-None-Match: "4be0ced0.1afc"\r\n
If-Modified-Since: Wed, 05 May 2010 03:50:08 CEST\r\n

Mongoose answers with a http 200 OK code and:
Last-Modified: Wed, 05 May 2010 03:50:08 CEST\r\n
Etag: "4be0ced0.1afc"\r\n

I've tried the same with my webserver at home (Cherokee). It answers with an 
304 Not Modified and closes the connection, which IMHO should be the right 
behaviour.

What version of the product are you using? On what operating system?
Dev version from around 2010-05-18

Please provide any additional information below.
Browser in this test was Google Chrome

Original issue reported on code.google.com by thenk...@gmail.com on 9 Jun 2010 at 4:36

GoogleCodeExporter commented 9 years ago
I've checked with Apache2 on the same embedded device than mongoose is running. 
It behaves exactly like Cherokee on my home server.
Overall the page refresh of Apache2 of course is still slower on this slow 
machine (at least in LAN). But over the internet the lack of caching may be a 
speed impact when running mongoose.

Original comment by thenk...@gmail.com on 10 Jun 2010 at 7:29

GoogleCodeExporter commented 9 years ago
Please try again with the recent source.

Original comment by valenok on 15 Jun 2010 at 9:53

GoogleCodeExporter commented 9 years ago
Latest source works on my short test. Thank you!

Original comment by thenk...@gmail.com on 15 Jun 2010 at 1:49

GoogleCodeExporter commented 9 years ago

Original comment by valenok on 23 Aug 2010 at 8:52