iis 7 - Is there a limit to Asp.Net 4.0 or IIS7 response redirect calls you can use in a row -
in our application have broken our app several modules. when logout.aspx page called, builds stack of logout pages call, 1 in each module. redirects each module's logout page redirects caller.
this has been working fine in our new app, uses aps.net 4.0 redirects seem stop working. fiddler shows redirect sent... browser doesn't send next get.
strange thing if remove , 1 module things work. doesn't matter remove, know no error occurring in of logout pages.
so, difference seems less redirects being used in row.
here final 302 browser receives... doesn't loginredirect.htm:
> /amsiweb/logoutcoordinator.aspx > http/1.1 accept: > application/x-ms-application, > image/jpeg, application/xaml+xml, > image/gif, image/pjpeg, > application/x-ms-xbap, > application/vnd.ms-excel, > application/vnd.ms-powerpoint, > application/msword, > application/x-shockwave-flash, */* > accept-language: en-us user-agent: > mozilla/4.0 (compatible; msie 8.0; > windows nt 6.1; wow64; trident/4.0; > slcc2; .net clr 2.0.50727; .net clr > 3.5.30729; .net clr 3.0.30729; media center pc 6.0; infopath.2; ms-rtc lm > 8; .net4.0c; .net4.0e) > accept-encoding: gzip, deflate > connection: keep-alive host: ustawvqa1 > cookie: > asp.net_sessionid=uf51gkiem0ditfvyi3pvkhoj; > geacsessionid=aa6be7f2-9bd5-4700-9a21-e9fa6c0a3b19; portalpathurl=; > portalpath=c:\inetpub\wwwroot\amsiweb\esiteweb\; aspsessionidqqrdqtcc=eimndbidiphcgcmfnhbohook; > .aspxauth=51c5f3fa040dfeddfb163d0df5b5f9d2aaab91ea76a5388bfe61bc54d83fef29eb3b0c7886fb473ef9391999d67921b5be0cea403f6ba00d5954d8e16bf054212ea4754c40f409473a3990d1a41867d9099ecd45ec229c6205c599727a5bfb19f6dd0ce72b8480ce1c13c10c7a39d50503420a79b70248df236403c5e632ce8d670dbef5f0f64f87141a546b8a471eaa163dea445f76ac6f36d36f7ec3ba805c > > > http/1.1 302 found cache-control: > private content-type: text/html; > charset=utf-8 location: > /amsiweb/logoutredirect.htm server: > microsoft-iis/7.5 x-aspnet-version: > 4.0.30319 set-cookie: .aspxauth=; expires=tue, 12-oct-1999 04:00:00 gmt; > path=/; httponly x-powered-by: asp.net > date: tue, 25 jan 2011 19:20:21 gmt > content-length: 144 > > <html><head><title>object > moved</title></head><body> <h2>object > moved <a > href="/amsiweb/logoutredirect.htm">here</a>.</h2> > </body></html>
my question... there limit response.redirects can use? if so, how change it... if not, have other ideas happening here.
(supposedly there answer on experts exchange)
i go under assumption it's browser stop, not web server. browsers ask, after couple of instances of, if you'd show more alert()
s, there may "safety" mechanism built-in assumes many redirects unsafe behavior.
i'm more inclined believe mention of visibility of location:
header being sent, no further get
request.
follow-up:
it appears exist in browsers. limits can changed minor tweaking, however. also, reading, ensure you're not creating redirect loop (/pagea.aspx doesn't redirect itself, or /pagea.aspx /pageb.aspx /pagea.aspx)
p.s. experts exchange, or one able locate, has answer link abandoned link (ironic given text in link)
Comments
Post a Comment