redirectmode

Why is HttpContext.Session null when redirectMode = ResponseRewrite

由 眉间皱痕 提交于 2019-11-28 07:18:41
问题 As is suggested elsewhere, I am using redirectMode = ResponseRewrite in my custom error configuration so my custom error page can access the exception info. This has worked like a charm for some time. In adding some more "help the user recover from an error" type functionality, we need a piece of info that has been previously stored in Session. When implementing this, I found that the various avenues to Session end in null when redirectMode=ResponseRewrite, but they are all populated when

CustomErrors does not work when setting redirectMode=“ResponseRewrite”

由 不打扰是莪最后的温柔 提交于 2019-11-26 19:36:39
In a old site, I was changing the way that CustomErrors works by adding redirectMode="ResponseRewrite" (new in 3.5 SP1): <customErrors mode="RemoteOnly" defaultRedirect="Error.aspx" redirectMode="ResponseRewrite"> <error statusCode="404" redirect="404.aspx" /> </customErrors> The thing is: it shows me the generic error page (the one that you get when you don't set customErrors . If I remove the redirectMode="ResponseRewrite" part, it works fine. I'm sure 3.5 SP1 is installed in the server, because I use the same setting on other sites hosted in the same server. Any ideas? Michael Hallock It is

CustomErrors does not work when setting redirectMode=“ResponseRewrite”

由 狂风中的少年 提交于 2019-11-26 08:58:56
问题 In a old site, I was changing the way that CustomErrors works by adding redirectMode=\"ResponseRewrite\" (new in 3.5 SP1): <customErrors mode=\"RemoteOnly\" defaultRedirect=\"Error.aspx\" redirectMode=\"ResponseRewrite\"> <error statusCode=\"404\" redirect=\"404.aspx\" /> </customErrors> The thing is: it shows me the generic error page (the one that you get when you don\'t set customErrors . If I remove the redirectMode=\"ResponseRewrite\" part, it works fine. I\'m sure 3.5 SP1 is installed
订阅 redirectmode