|
Home > Archive > IIS Server > February 2004 > 2nd try: HTTP Header 'Expires after' x days--after when?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
2nd try: HTTP Header 'Expires after' x days--after when?
|
|
| Michael Flanagan 2004-02-05, 11:36 am |
| I posted this earlier (as part of a larger question) and got some good
feedback from Egbert Nierop, but I still have an open question:
I go into the properties for an object (Internet Information
Services), such as a .jpg file, or even a directory, and go to the
HTTP Headers tab, I check 'Enable content expiration.' One of the
choices is 'Expire after', where I can then specify a number of
minutes, days, etc. 'Expire after' when? After the user first
requests it? After the object's creation date? After its modified
date? After some other date/time?
Thanks!
Michael
Regards,
Michael
mflanagan@MJFlanagan.nospam.com
<remove the 'nospam'>
| |
| Jerry III 2004-02-05, 4:34 pm |
| Why don't you check that yourself?
Just use WFetch (part of IIS 6 RK, but it's downloadable on its own) or
wfetch or even telnet and request the file. Then check the response headers.
Jerry
"Michael Flanagan" <mflanagan@MJFlanagan.delete.this.nospam.com> wrote in
message news:4022dd3a.28381089@news.viawest.net...
> I posted this earlier (as part of a larger question) and got some good
> feedback from Egbert Nierop, but I still have an open question:
>
> I go into the properties for an object (Internet Information
> Services), such as a .jpg file, or even a directory, and go to the
> HTTP Headers tab, I check 'Enable content expiration.' One of the
> choices is 'Expire after', where I can then specify a number of
> minutes, days, etc. 'Expire after' when? After the user first
> requests it? After the object's creation date? After its modified
> date? After some other date/time?
>
> Thanks!
>
> Michael
> Regards,
> Michael
>
> mflanagan@MJFlanagan.nospam.com
> <remove the 'nospam'>
>
| |
| Michael Flanagan 2004-02-06, 4:38 am |
| Jerry,
Thanks for the info. In answer to your question: I couldn't concoct
the correct 'HEAD' or 'GET' command in telnet (my fault, naturally),
and I didn't know WFetch existed. I just downloaded WFetch and used
it. The 'when' date/time seems to be the date/time the server served
the object.
Thanks again.
Michael
On Thu, 5 Feb 2004 21:11:52 -0800, "Jerry III" <jerryiii@hotmail.com>
wrote:
>Why don't you check that yourself?
>
>Just use WFetch (part of IIS 6 RK, but it's downloadable on its own) or
>wfetch or even telnet and request the file. Then check the response headers.
>
>Jerry
>
>"Michael Flanagan" <mflanagan@MJFlanagan.delete.this.nospam.com> wrote in
>message news:4022dd3a.28381089@news.viawest.net...
>
>
Regards,
Michael
mflanagan@MJFlanagan.nospam.com
<remove the 'nospam'>
| |
| Jerry III 2004-02-06, 12:34 pm |
| No problem. There's a lot of tools to dump an HTTP request, Wfetch is one of
the easier to use (and actually quite powerful). You can use it to
troubleshoot problems (or questions) with HTTP headers...
Jerry
"Michael Flanagan" <mflanagan@MJFlanagan.delete.this.nospam.com> wrote in
message news:4023cdc7.89962809@news.viawest.net...
> Jerry,
>
> Thanks for the info. In answer to your question: I couldn't concoct
> the correct 'HEAD' or 'GET' command in telnet (my fault, naturally),
> and I didn't know WFetch existed. I just downloaded WFetch and used
> it. The 'when' date/time seems to be the date/time the server served
> the object.
>
> Thanks again.
>
> Michael
>
> On Thu, 5 Feb 2004 21:11:52 -0800, "Jerry III" <jerryiii@hotmail.com>
> wrote:
>
headers.[color=blue]
>
> Regards,
> Michael
>
> mflanagan@MJFlanagan.nospam.com
> <remove the 'nospam'>
>
|
|
|
|
|