today i had go at upgrading a 0.6.9 app (which used a very old patch
to make x-accel-redirect work with radiant's ResponseCache) to 0.8.1
and ran into (what i'm guessing is) an issue with radiant::cache,
:use_x_accel_redirect option and firefox. under the following
conditions firefox will receive a response with an
application/octet-stream content-type header and prompts me to save an
"untyped data" file.
1. rm -rf tmp/cache/*/*
2. load a page in firefox
3. verify entity and meta cache entries were created
4. reload the page
- 304 not modified response
- see the custom "X-Accel-Redirect" header i set in nginx
- see all the headers set by radiant
5. edit and save the page that has been cached
6. verify that new entity and meta cache entries were created
7. reload the page and get prompted to save "untyped data"
(i'm guessing that step 5 could be replaced by waiting five minutes
for the cache to expire)
i've only been able to reproduce this in firefox (versions 1.0.7,
1.5.0.7, 2.0.0.20, 3.0.12 and 3.5.6) which seems to be the only
browser (and i tested in about 15 different versions of various
browsers) that gets a 304 response when clicking the reload button.
has anyone else experienced similar behavior or have any advice on
what i'm doing wrong in my configuration? the relavent bits are:
environment.rb
config.middleware.use ::Radiant::Cache, :use_x_accel_redirect => '/entity'
nginx.conf
location /entity {
internal;
root /radiant/tmp/cache;
}
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
