It turns out IE7 has the same problem. I was just getting started looking at a new part of our system in IE6 and I was doing an extremely simple rescue (just printing the Exception message). Our standard rescues have enough content on them that they're always over 512 bytes, which is what led me to believe the problem was unique to IE6. Thanks for your help.
On Mar 25, 2:49 pm, Ryan Scott <[email protected]> wrote: > Thanks. I don't typically have to target IE 6, so this hasn't popped > up before. > > On Mar 25, 1:48 pm, Mauricio Scheffer <[email protected]> > wrote: > > > Make sure the content length of the rescue response has at least 512 > > bytes. > > Seehttp://support.microsoft.com/?scid=kb;en-us;294807 > > > On Mar 25, 4:39 pm, Ryan Scott <[email protected]> wrote: > > > > Unfortunately, I have to code against Internet Explorer 6 which > > > occasionally presents some interesting issues. > > > > One of these is the fact that the option "Show Friendly Http Error > > > Messages" prevents rescues from rendering properly. Instead it's a > > > general HTTP 500 Internal server error message. > > > > I can always use a rescue controller and manually set the status back > > > to 200 to show the rescue I intend, but I am wondering if there is a > > > better option. Has anyone else run into something like this? Is > > > there an elegant way of handling it? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
