/ trailer my two cents

About my post this morning. I received some nice comments and advices, but the problem is that nobody get it.

I give as an example a link to a site I develop but this happens to every bleeping site ;-)

Try this one and compare with the original and this one and again compare with the original.
So you see by yourself !

I know that I am surrounded by windows developers but believe me in web development it's really a BAD idea to let something like this happening.
The only site who managed to retrieve this as a 404 error is ASPalliance. No idea how they did .

It really seems for me to be a bug. And finally to answer to somebody, it appears that the whole <head> section is screwed.
Classic example is when the page has a javascript declared in the head section.

It seems trivial but think about my aunt Marge who never learn to type correctly a URL address ;-)

 

3 Comments

  • Happy to see that at least one person agreed with my post ;-)

    This should return a 404 error, not a useless and definitively bad page !

  • I believe I get what you are saying and here is my two cents. I don't know this for fact, but it's an observation.



    My guess is that the &quot;/&quot; at the end of URL is by design. I think it helps with accessibility. For example, by placing the &quot;/&quot; at the end of the URL, it disables the stylesheets allowing the browser to control the font size and etc. of the web page. I think it's a pretty cool feature because so many sites get hung up on &quot;look and feel&quot; that they forget about accessibility and usuability. As a result, a lot of sites use really tiny fonts and I never can read them. Now that I know this little trick, I can override their styles and get decent font sizes.



    But, this doesn't explain the missing content on the MSDN link you provided. But, on your original post, by including the &quot;/&quot; I did receive a JavaScript error and therefore, maybe it also stops the execution of JavaScript during the page load. I think this would make sense with the MSDN link you provided because the menu was missing and if I'm not mistaking, that memu is built dynamically using JavaScript.



    Just a thought.

  • Again, really, I think this has to do with the relative url, as said before in your other post.



    Why don't you test if by setting this base tag? You (Paschal) said it didn't have to do anything with it, but I think it does.



    Although I also thing blah.aspx/ should give an error, some way the server still knows what page you actually want. Or something like it! :)



    Why MSDN doesn't show the menu, is probably because of the HTTPHandlers. .Text uses (kinda) the same way of figuring out where you are. Have you ever looked at it? All your folders and .aspx files aren't there! By using a regular expression in the HTTPHandlers, it figures out what page you actually want and displays this at the location you asked for it. Works very, very nice!

    Only the weblogs.asp.net/posts/ folder exists (or something like it) and when you look up an .aspx file in your weblogs.asp.net/*/posts/?.aspx it looks at the ? which number it is, knowing what item it should get from the database.



    This works very good for this weblog, as the administrator only has to create your username and weblog location in the database. Without creating any folder and without copying any file, you have your weblog! :)



    MSDN probably uses HTTPHandlers to look at the url you request, picks this up and adds the menu and header. Or... it's in the javascript, which it can't load because of the relative path it misses.



    But then again, you constantly keep repeating the header of your html is missing. But I still can see everyting between the &lt;head&gt; tags, including some javascript library and/or css files.

Comments have been disabled for this content.