bad urls behind load balancer
Posted: Thu Sep 17, 2009 11:22 am
Our app runs behind a BigIP f5 load balancer that also handles ssl for our site.
So, when a request is made to
https://fakeurl.com/fakepage.aspx
the F5 takes the request, repackages it and sends it to one of the webservers as
http://fakeurl.com:8443/fakepage.aspx.
Under this setup the web report designer is generating links and post backs that look like this
http://fakeurl.com:8443/fakepage.aspx?s ... _OETags.js
instead of
https://fakeurl.com/fakepage.aspx?stimu ... _OETags.js
The problem is the F5 will not let this request through so the desinger will not work.
We have about 4 weeks until our go live date. Is there anything that currently exists or could be added, allowing us to tell the report desinger to use relative urls or set the base url it should use?
So, when a request is made to
https://fakeurl.com/fakepage.aspx
the F5 takes the request, repackages it and sends it to one of the webservers as
http://fakeurl.com:8443/fakepage.aspx.
Under this setup the web report designer is generating links and post backs that look like this
http://fakeurl.com:8443/fakepage.aspx?s ... _OETags.js
instead of
https://fakeurl.com/fakepage.aspx?stimu ... _OETags.js
The problem is the F5 will not let this request through so the desinger will not work.
We have about 4 weeks until our go live date. Is there anything that currently exists or could be added, allowing us to tell the report desinger to use relative urls or set the base url it should use?