-----Original Message-----
From: william.wells <[EMAIL PROTECTED]>
To: Magowan, Richard M. (ITS) <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, May 25, 1999 10:35 PM
Subject: RE: DCOM on Gauntlet
>FYI: I first noticed the strings "If-Modified-Since:" and "If-None-Match:"
>in Microsoft IE 4.0 browser. It appears to be an attempt to optimize
network
>traffic by keeping the page from being downloaded if the browser has the
>most recent version (instead of using a HEAD function and comparing
>modification times and then resending the GET function). If the page hasn't
>been modified on the server, the server sends a reject back to the browser
>and the browser uses the cached version of the page.
>
>I haven't had a problem running through Gauntlet (4.1) with these strings.
I
>believe there is a configuration setting to tell Gauntlet to toss all
>non-standards header fields - you might want to check your configuration.
>While I haven't kept up on the standards, I don't think these are standard.
They most certainly are standard, at least If-Modified-Since: is.� Never
heard of If-None-Match.� IMS is specified in HTTP/1.0.
>Not sure if this affects DCOM or not. Haven't had to deal with that yet.
It doesn't.� DCOM, while it may be tunnelled through HTTP, is not HTTP.
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
