Skip to main content

JSP error-page and Internet Explorer

I hate Microsoft. You might have heard that a zillion times in the developer world, especially in the non-microsoft-technologies world. But yesterday, I felt like killing myself because of Microsoft's IE.

Here is what is happened. I was writing an error page for handling a custom Exception in filter.

<error-page>
<exception-type>com.so.testapp.exception.CustomException</exception-type>
<location>/error.jsp</location>
</error-page>

and the JSP has it simple too..

<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<c:set var="cException" value="${requestScope['javax.servlet.error.exception']}"/>
Got Exception : <c:out value="${cException}" />

This must be pretty darn simple but IE comes with this *Friendly* error page.

I have had a nightmare trying to figure out why I dont get my message, Only to realise that there is 512k size threshold before which IE hijacks *your* custom error page. It WILL tell you that your website has a programming error as MOST LIKELY CAUSE. I kept working on what that programming error could be. I know I cannot blame IE for my naive acceptance of defeat.

But FF comes up for rescue. It doesnot meddle with your data, showing its own Friendly Error pages instead of YOUR Friendly Error Pages.


Better stick with the one that is *Friendly*.

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>