corrupted request header problem

We have a .net application that reads the If-Modified-Since header via
context.Request.Headers.Item("If-Modified-Since"). The resulting
string sometimes has appended to it "; l", after a normally valid date
string. We are temporarily working around it by parsing the string,
but I would really like to know if anyone else has seen this behavior,
or may know why it is happening. Running 32-bit Win2003 Server SP2,
app is .net 1.1.

Thanks,

Brian

Re: corrupted request header problem

On Sep 24, 12:09 pm, brianklip...@gmail.com wrote:
> We have a .net application that reads the If-Modified-Since header via
> context.Request.Headers.Item("If-Modified-Since"). The resulting
> string sometimes has appended to it "; l", after a normally valid date
> string. We are temporarily working around it by parsing the string,
> but I would really like to know if anyone else has seen this behavior,
> or may know why it is happening. Running 32-bit Win2003 Server SP2,
> app is .net 1.1.
>
> Thanks,
>
> Brian


Actually, I see that you have no choice but to parse and remove the
";".
- It could be coming from the client, and you certainly can't change
the client.
- It could be coming from the server API, and you certainly can't
change the server API.

I do not believe it comes from the server API because there's no code
in IIS/ISAPI that will introduce a trailing semi-colon, and I have not
seen that behavior from ASP nor ASP.Net.

I believe you are seeing the ";" from the client. You can try to
verify this by temporarily adding something with .AppendLog() whenever
you see a trailing";" and later filtering through the IIS log files to
see if those requests match certain user-agent string.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: corrupted request header problem

On Sep 24, 9:10 pm, David Wang wrote:
> On Sep 24, 12:09 pm, brianklip...@gmail.com wrote:
>
> > We have a .net application that reads the If-Modified-Since header via
> > context.Request.Headers.Item("If-Modified-Since"). The resulting
> > string sometimes has appended to it "; l", after a normally valid date
> > string. We are temporarily working around it by parsing the string,
> > but I would really like to know if anyone else has seen this behavior,
> > or may know why it is happening. Running 32-bit Win2003 Server SP2,
> > app is .net 1.1.
>
> > Thanks,
>
> > Brian
>
> Actually, I see that you have no choice but to parse and remove the
> ";".
> - It could be coming from the client, and you certainly can't change
> the client.
> - It could be coming from the server API, and you certainly can't
> change the server API.
>
> I do not believe it comes from the server API because there's no code
> in IIS/ISAPI that will introduce a trailing semi-colon, and I have not
> seen that behavior from ASP nor ASP.Net.
>
> I believe you are seeing the ";" from the client. You can try to
> verify this by temporarily adding something with .AppendLog() whenever
> you see a trailing";" and later filtering through the IIS log files to
> see if those requests match certain user-agent string.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //

Thanks David