New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resource mapping doesnt work #12
Comments
Also as per the tracing even the request is from loadbalance, in request server port is still 88(prob because website is hosted on 88) but with servername as lbhostname. |
We do request uri validation. Your load balancer should be rewriting the request uri befor forwarding it, i assume it does not. I don't know what the asp.nethttp://asp.net hosting does to allow manual overrides. I don't think it does anything, so you may be able to overwrite yourself the request data in a pipeline contributor registered before uri mapping. Note that you'd have to make sure you run on the latest code and not some random outdated 2.0 version. Seb On 4 Mar 2013, at 13:53, "amrender" <notifications@github.commailto:notifications@github.com> wrote: I am using Loadbalance which forward the requests to site running on port 88 IIS7.5. Load balancer setup I have compared the request on the server using trace.axd, and can see only ServerName server variable as possible reason for mapping to fail. Any ideas. — |
I guessed it. |
my requirement is should be accessible from loadbalance as well as serverhost name, not sure if pipeline can be smart enought to manage that. |
You have to write it yourself the feature does not exist. Seb On 4 Mar 2013, at 14:32, "amrender" <notifications@github.commailto:notifications@github.com> wrote: my requirement is should be accessible from loadbalance as well as serverhost name, not sure if pipeline can be smart enought to manage that. — |
do u mean KnownStages.IUriMatching |
yes Seb On 4 Mar 2013, at 15:47, amrender <notifications@github.commailto:notifications@github.com> wrote: do u mean KnownStages.IUriMatching — |
I am using Loadbalance which forward the requests to site running on port 88 IIS7.5.
Resource mapping works fine if request using serverhostname:88/resource, but if I user LBHostName/resource, i always get 404.
Load balancer setup
LBHostName = serverhostname:88
I have compared the request on the server using trace.axd, and can see only ServerName server variable as possible reason for mapping to fail.
I was thinking to add pipeline to override serverName variable. What do you think.
Any ideas.
The text was updated successfully, but these errors were encountered: