vADC Forum

Reply
Contributor
Posts: 32
Registered: ‎03-26-2013
Accepted Solution

Host, a very special Header

It seems there are odd cases where changing the Host header is silently not allowed.

I found at least two places where I could NOT change this header before STM forwards a request to a backend:

* http.request.head(url, [ headers ], [ timeout ]) (and I suppose http.request.get()) do not accept a Host header in the optional "headers" argument. This can be a real problem since I guess people use it to craft custom requests.

* http.setHeader("Host", "hostheader") does not rewrite the Host header when it happens in a Request rule of an SSL Decrypting Virtual Server.

Not sure why those limitations. Can someone confirm the problem? Will this be allowed in the future? There are ways to circumvent the issue but it's not as elegant.

Cheers,

Sameh.

Highlighted
Frequent Contributor
Posts: 180
Registered: ‎11-29-2012

Re: Host, a very special Header

Sameh,

Do you have some code samples you can share to illustrate these points?

As an aside, if the functions aren't working as described, I would consider the problems to be bugs, and I would LOVE you to raise a support ticket to get them looked at..

A.

Contributor
Posts: 32
Registered: ‎03-26-2013

Re: Host, a very special Header

Thank you for your answer Aidan.

Actually I cannot reproduce those issues when I use a fresh configuration designed to exhibit this behavior. I thought I had looked at all caveats already but it seems I should dig further!

I will get back here once I find the ugly truth about my rules!

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.