• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Wrong caching headers in browser
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Wrong caching headers in browser


  • Subject: Re: Wrong caching headers in browser
  • From: OC <email@hidden>
  • Date: Sat, 24 Jan 2015 02:37:00 +0100

Chuck,

On 24. 1. 2015, at 2:32, Chuck Hill <email@hidden> wrote:

> First guess would be your mod_expires configuration in Apache.  Apache can, and will, override the headers that the app sends.
> http://httpd.apache.org/docs/2.2/mod/mod_expires.html

If I were receiving proper headers through direct access and wrong ones from Apache, that would self-evidently be the culprit; but how comes I get the proper headers from curl through Apache using precisely the same URL? :-O (That's why I'm adding -A so that the request indeed looks like it comes from Safari.)

Anyway thanks a lot, I'll send the info to the server admins.

All the best,
OC

> On 2015-01-23, 5:21 PM, "OC" wrote:
>
> Hello there,
>
> in my image URL direct action, I set up caching headers in my WOResponse so that the client caches the image. When I have a look through curl, I _am_ getting those headers all right:
>
> ===
> 54 /tmp> curl -sD - -o /dev/null 'http://aukce1.fskprojektova.cz/cgi-bin/WebObjects/REBOISx.woa/wa/banner?size=103747&mkpk=1000002&lang=CZ' -A 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.71 (KHTML, like Gecko) Version/6.1 Safari/537.71'    HTTP/1.1 200 Apple
> Date: Sat, 24 Jan 2015 01:16:07 GMT
> Server: Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/0.9.8y
> cache-control: private, max-age=36000
> expires: 2015-01-24 03:16:07 Etc/GMT
> content-length: 103747
> MS-Author-Via: DAV
> Content-Type: image/png
>
> 55 /tmp>
> ===
>
> It does not seem to work in browser though -- Safari shows me the response headers for the very same URL in a different (and wrong) way:
>
> PastedGraphic-7.tiff
>
> Has anybody the slightest idea what might be the culprit?
>
> Note: the problem does not seem to be local to my computer/browser -- another user reported the same (wrong, as in the screenshot) headers in his Chrome.
>
> Thanks a lot,
> OC
>


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Re: Wrong caching headers in browser (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Wrong caching headers in browser
  • Next by Date: Re: Wrong caching headers in browser
  • Previous by thread: Re: Wrong caching headers in browser
  • Next by thread: Re: Wrong caching headers in browser
  • Index(es):
    • Date
    • Thread