• Post Reply Bookmark Topic Watch Topic
  • New Topic

Strange Internet Explorer behavior  RSS feed

 
Chad Foor
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a rather odd situation here. I support a web site that contains a
variety of static content and .jsp files in a central location.

I was asked to create a 'testbed' site with a directory structure like so:

Original Layout:
mainsite (top level) - /WEB-INF/...
- index.jsp
- /resources/...

New Layout:
mainsite (top level) - /WEB-INF/...
- index.jsp
- /resources/...
- /mirrorSite/ (and various subdirectories)

There's nothing that I introduce into the mainsite's web.xml file.

Everything in the mirrorSite set of directories is a set of simple
static content and .jsp files that dont have anything more elaborate
inside than referencing <jsp:include> directives here / there.

Here's the rub though. When I reference the mirror site (you'd have
to know it was there) - http://www.myMainSite.org/mirrorSite/

I can see the stuff for the mirrorSite on Firefox/Netscape browsers,
yet all I get is a blank page when I try to reference this location from
Internet Explorer. What is more odd, when I look at the page source for
the 'supposedly' blank page, I get the correct page source that I wanted
there. (IE just didnt render this correctly.) Even stranger, when I reference the main site from IE, I do see the original mainsite content.

Is this something I can set some sort of exotic option in IE and get it
to work ??

Appreciate any inputs.

Thank you.
Chad
 
Ben Souther
Sheriff
Posts: 13411
Firefox Browser Redhat VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would start by comparing the generated HTML output from the two apps.
If you have one available, use a diff program. It might catch something that your eye is missing.

Also, how did you set up the paths in your include actions?
If they're relative to the page, moving the page to a new directory may be keeping the resources from being found.
 
Chad Foor
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, I was very careful about the <jsp:include> directives.

A colleague at work was telling me that older versions of IE dont deal
well with the <!DOCTYPE xhtml declarations at the top of JSP files.

(I think that was I was dealing with. I changed the xhtml declarations to their more loosy-goosy html transition equivalent.)

So far, this appears to work fine. Just boggles my mind that the version
of IE I was dealing with on my desktop didnt have any problems with the
original site.
 
Bear Bibeault
Author and ninkuma
Marshal
Posts: 66152
146
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Chad Foor:
Just boggles my mind that the version
of IE I was dealing with on my desktop didnt have any problems with the
original site.


I could get up on a soapbox big-time about this, but suffice it to say that with all the micro-updates that get made to IE, there are myriad different quirky behaviors that are possible. We get some support calls from client using IE that are truly astounding in that just basic things stop working in their particular configuration.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!