URL STrangeness (IE 6)

Topic

New Reply

I have a web site that uses and has a URL http://www.teacherscouncil.govt.nz/cnc/index.stm#top%5B/url%5D to reference it.

In IE 6.0 this gives me an IE error if entered via the browser window with cut and paste – despite the fact that the base URL http://www.teacherscouncil.govt.nz/cnc/index.stm%5B/url%5D is there, and works when fired as a new window as in Woody’s Lounge.

Anyone got a clue what I’m doing wrong?

Reply | Quote

Replies

I get no error message and the page loads normally when I paste the URL http://www.teacherscouncil.govt.nz/cnc/index.stm#top into the address bar in a new browser window.

What is the text of the error message you get?

Reply | Quote

[Edited to reduce picture size and clarify the text].

Note that this is not a new window, rather it is a paste over a previous window that is not the current one and #top was at the end rather than the full-stop.

Reply | Quote

I hope someone else can help, as I do not get that error, and although Google has many hits for this error message, I couldn’t find a solution.

Reply | Quote

(Edited by jscher2000 on 13-Nov-06 13:13. Added link.)

I can replicate the error by:

(1) Displaying Google.com;
(2) Pasting http://www.teacherscouncil.govt.nz/cnc/index.stm#top into the address bar; and
(3) Pressing Enter.

The strange thing is, it appears that the desired page has indeed been displayed when the error dialog pops up in front of it. And also strange: Firefox doesn’t object.

I think there is a server configuration issue. If I load that URL using Rex Swain’s HTTP Viewer, I get back HTTP/1.1

Reply | Quote

Thanks Hans and Jefferson

Everything I found on the web seem to indicate that there is something funny relating to JScript, IE and context – including the speed at which users move the mouse.
Using a new browser window doesn’t exhibit the problem, re-using the same one often does (but occasionally doesn’).

This same construct works fine on other parts of the site – it is only that one #top that fails. I will do some work around fixing context.

(.stm was an extension that our web-site developers used for server pages. On the development site they have a lot of symbolic code, but when published to the public site this disappears and the remainder is valid HTML and scripts.) The public site is a microsoft site (which is a mystery to me too) while the development one is (open source and also a mystery) .

Reply | Quote