Re: Trouble using Apache 2.0 to proxy IIS 6.0
From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 04/02/04
- Next message: David Wang [Msft]: "Re: Disable TRACE??"
- Previous message: Ivan: "Re: IIS5 unc virtual directories"
- In reply to: djmv_at_yahoo.com: "Trouble using Apache 2.0 to proxy IIS 6.0"
- Next in thread: Mark Vaughn: "Re: Trouble using Apache 2.0 to proxy IIS 6.0"
- Reply: Mark Vaughn: "Re: Trouble using Apache 2.0 to proxy IIS 6.0"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 1 Apr 2004 17:15:19 -0800
Use a Network Trace program like NetMon, included with Windows Server 2003,
to monitor network traffic for the failing case. It should be able to tell
you exactly what is going wrong.
Honestly, I would first look at whether the Apache reverse proxy is properly
sending data back and forth since you have NO problems going directly
against IIS6. Different client configuration is expected in the real world,
so the reverse proxy should handle it all -- after all, the end-server is
able to handle it.
-- //David IIS This posting is provided "AS IS" with no warranties, and confers no rights. // <djmv@yahoo.com> wrote in message news:a91c9c82.0404011635.683aeea@posting.google.com... I am having multiple issues using Apache 2.0 to proxy requests to IIS 6.0. We had to move to Apache 2.0, because other proxies had serious performance issues proxying to IIS 6.0 if "Use HTTP/1.1" was set in the browser. Current problem involves POSTs. 99% of users can POST just fine, but a few have issues if the POST is over about 1600 bytes and has to break into multiple packets. In this scenario, we actually lose packets and the POST will fail due to malformed data (missing data). On one of the PC's that didn't work, we tried via dialup and all worked fine. That points to local network configuration issues on the PC, since IE and Mozilla yield same results. To further support this theory, once PC that worked died, and after an OS re-install it longer worked. Everything but POSTing files works on the effected PC's. Now, to throw a wrench in that, I setup a test to allow a few of the effected users to hit IIS 6.0 directly, and the issue went away. Any ideas? I think this is a combination of Apache 2.0 Proxy and local PC configs. HELP -Mark
- Next message: David Wang [Msft]: "Re: Disable TRACE??"
- Previous message: Ivan: "Re: IIS5 unc virtual directories"
- In reply to: djmv_at_yahoo.com: "Trouble using Apache 2.0 to proxy IIS 6.0"
- Next in thread: Mark Vaughn: "Re: Trouble using Apache 2.0 to proxy IIS 6.0"
- Reply: Mark Vaughn: "Re: Trouble using Apache 2.0 to proxy IIS 6.0"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading