(Ovid - response to IIS responses) Re: IIS and Apache

Responses:

merlyn: I've installed CGI.pm 2.74 on the box in case that was the problem. Didn't help. I suggested using NPH to deal with this since it looks like a server issue, but that idea was vetoed.

chromatic: I tried uri instead of location and that made it worse! The header reported Location: uri Ack! Of course, that was before I upgraded to 2.74, so I'll try it again after Xmas.
extremely: I like that idea! I'll give that a shot, too.

IIS: whudda piece of work. Can anyone think of any valid reason why it should report different versions of the HTTP protocol? Not to mention its apparent munging of headers -- though the jury's still out on that.

Amusingly, when I upgraded CGI.pm, I noticed CGI::Utils. Hmm, what's that?

I opened it up and noticed, amongst other things, that it includes EBCDIC support. Immediately, my eyes rolled into the back of my head and I started foaming at the mouth. Fortunately, the IS director rushed over and whispered "no more mainframes" over and over until the convulsions subsided. Whew! That was scary.

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

Comment on (Ovid - response to IIS responses) Re: IIS and Apache

Replies are listed 'Best First'.
Re: (Ovid - response to IIS responses) Re: IIS and Apache by extremely (Priest) on Dec 24, 2000 at 15:08 UTC
Oh, don't blame IIS on the headers thing, Apache has to do the same thing... <IfModule mod_setenvif.c> # The following directives modify normal HTTP response behavior. # The first directive disables keepalive for Netscape 2.x and brow +sers that # spoof it. There are known problems with these browser implementa +tions. # The second directive is for Microsoft Internet Explorer 4.0b2 # which has a broken HTTP/1.1 implementation and does not properly # support keepalive when it is used on 301 or 302 (redirect) respo +nses. # BrowserMatch "Mozilla/2" nokeepalive BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-respon +se-1.0 # # The following directive disables HTTP/1.1 responses to browsers +which # are in violation of the HTTP/1.0 spec by not being able to grok +a # basic 1.1 response. # BrowserMatch "RealPlayer 4\.0" force-response-1.0 BrowserMatch "Java/1\.0" force-response-1.0 BrowserMatch "JDK/1\.0" force-response-1.0 </IfModule> [download] I've got a lot of gripes with IIS but broken clients just something you have to deal with. In fact, that brings up another thought. Have you tried sending different User Agent strings to IIS with that request? That may be part of the problem too. Yah never know when you can't muck with the innards. -- $you = new YOU; honk() if $you->love(perl)	[reply] [d/l]
Re: (Ovid - response to IIS responses) Re: IIS and Apache by mwp (Hermit) on Dec 24, 2000 at 05:15 UTC
That IIS is reporting HTTP/1.0 at one point and 1.1 at another makes me think that it's possible that two instances of IIS are running in the background. It may even be possible that one of these instances of IIS is 3.0! Then again, I may be horribly off base--but in any case you might try completely uninstalling and reinstalling IIS 4.0. Good luck. =)	[reply]