Topic: proxy pass

[martind]

Hi
Was wondering if anyone could point me in the right direction here.
I am using proxypass in sme server to redirect to an IP of a VM in the local network.
Once the users try to log in to the accessed web page they get following error

Bad Request. Size of a request header field exceeds the server limit



This usually gets resolved by clearing the cache how ever that does not fix the problem.

The website works on LAN when accessed via IP address.
It does work on LAN and also remotely when accessed via URL provided the cache and cookies have been cleared before accessing it.
This issue has been there since initial set up.

The proxypass domain is as follows:
db domains setprop http://name.domain.com.au ProxyPassTarget http://xxx.xxx.xxx.xxx/

No alias/directory proxypass has been set up in this case.

and no custom template fragment

details of public DNS entries are as follows:
http://name.domain.com.au

Website runs in IIS6 in Local VM Windows server 2008. SME is redirecting the traffic to it using the proxypass.


Any suggestions would be greatly appreciated.
thanks

[mmccarn]

We'd need more info to be helpful.

* Does the website work when accessed from the LAN (not using proxypass at all)?
-> Can you access it locally using the same URL that you use remotely, or do you use a different URL (IP address or local hostname)?

* Did this configuration work, then stop working, or has it never worked?
-> if it used to work, when did it stop (what changed)?

* What are the details of your proxypass configuration?
-> Domain proxypass?
-> alias/directory proxypass?
-> custom template fragment similar to the outlook web access example?

* What are the details of any public DNS entries used to access the proxypass address (or do you access it by IP address)?

[CharlieBrady]

Once the users try to log in to the accessed web page they get following error

Bad Request. Size of a request header field exceeds the server limit

This is an issue with the destination web server and the application which is running on it. It's generating cookies which are larger than what it itself can handle. The browser is (probably) just returning cookies sent by the server.

Nothing to do with SME server, which is just providing the pipe to connect the browser and the destination web server.

You could try clearing cookies in the browser which is being used to access the website. There might be some corrupt cookies.

[martind]

Just clarifying:

The website works on LAN when accessed via IP address.
It does work on LAN and also remotely when accessed via URL provided the cache and cookies have been cleared before accessing it.
This issue has been there since initial set up.

The proxypass domain is as follows:
db domains setprop http://name.domain.com.au ProxyPassTarget http://xxx.xxx.xxx.xxx/

No alias/directory proxypass has been set up in this case.

and no custom template fragment

details of public DNS entries are as follows:
http://name.domain.com.au

Website runs in IIS6 in Local VM Windows server 2008. SME is redirecting the traffic to it using the proxypass.

Thank you

[CharlieBrady]

martind, you are not telling us the proper facts. I do not believe that you are using (literally) name.domain.com.au, and I do not believe you are really using 'http://xxx.xxx.xxx.xxx/' as the proxy pass target.

and also remotely when accessed via URL provided the cache and cookies have been cleared before accessing it.

As already stated, SME server is doing what it needs to do. The fault is with the destination webserver or application.

If you tell us the actual URL you are using, someone else might be able to diagnose which cookie is actually causing the problem.