Problem with some Pages? - Re: More piccies

"Tickettyboo" <tickettyboo@xxxxxxxxxxxxx> wrote in message
news:3qdgsoFe5dn7U1@xxxxxxxxxxxxxxxxx
> In news:xteqa0gejsb$.907y9ui7frcd$.dlg@xxxxxxxxxx,
> MCC whispered softly in my ear...:
>> On Mon, 3 Oct 2005 15:22:57 +0100, biffo wrote:
>>
>>> Just to bore you, or give you something to look at. ;-)))LOL
>>>
>>> http://sites.ecosse.net/biffos21/brt
>>
>> I have a problem viewing those pictures and your Aberdeen ones
>> in Firefox, Biffo.
>>
>> I can see your page of thumbnails no problem but when I click on
>> any of them to see a bigger version I get a blank screen apart
>> from the frame round where the picture should be and, in the top
>> left-hand corner, a small graphic that shows a broken link.
>>
>> Don't know if the techies can make anything of this or not -
>> when I put my cursor over the first thumbnail in Firefox I get this
>> link in the status bar
>> http://sites.ecosse.net/biffos21/brt/main\01.htm
>> - *note the backward slant before 01.htm*
>> but when I do the same thing in Internet Explorer 6 I get an
>> identical URL except for the last part
>> http://sites.ecosse.net/biffos21/brt/main/01.htm
>> -*all forward slants*
>>
>> What's going on, techy people?
>
> Not a techy, more a 'nosey' I looked at the source code. What you
> are seeing in Firefox is what is written in the html.

Yep, or to be more exact, what the *Browser* is seeing in the HTML
that it has Received...

Remember that the HTML that is in the Browser has passed through several
different stages on the way from the Server, any (or all) of which may
have altered (Filtered) the HTML.

For example, many Firewalls include Web Filtering stuff.
& Ad Blockers, PopUp Stoppers & things like that will (as a matter
of course) change - *ReWrite*! - the HTML of each & every Page that
you see in the Browser.

& it is the Browsers job to *faithfully* (& accurately) Interpret
the HTML that it is given (by the Server/Intermediate Proxy
& Filtering stuff) correctly & display the Page, as described by
the HTML...

>... Maybe IE is more forgiving of things like that

Yep, IE is definitely very lax on displaying HTML exactly as it is -
it will take loads of things which are actually incorrectly written
& then *attempt* to try & guess what was meant to be written.

>... and interpreted it correctly,

Well, some people (the people who wrote & defined the published HTML
Standards) would say that it has interpreted it *incorrectly*? -
If it tries to guess at stuff & display things in a way that wasn't
actually specified in the HTML.

>... whereas Firefox just reads it and isn't able to show you
>anything cos it doesn't make sense?

Which, surely is the correct way that it should be done?

Who is to say that something like Internet Explorer can *guess* what
was really meant to be written?

What Rules does it use to define what it uses instead of what is
actually there?

& how can people be sure that it won't guess something wrongly & display
the *wrong* thing???

What if it (erroneously) showed up some Pornographic Pic, that was on
the same (Shared) Server, which just happened to have a single Character
different in its File Name?

Anyway...
On with the actual reason for the prob...

I'm intrigued & puzzled by this prob, cos I also noticed that there was
a *Back*Slash in the HTML Code (in my Browser), though when Internet
Explorer was asking the Server for them, it sent the HTTP Requests with
*Forward* Slashes!

As it happens, that's actually only to be expected, cos most (Unix)
based Web Servers *do* use (only) Forward Slashes as the Directory
Delimiters.

However, the Server that is Hosting the Ecosse.net Site(s) is a Server
Running *windoze* based Server Software... "Microsoft-IIS/4.0" (which is
an old Version of the Microsoft Internet Information Server Software).

So it doesn't actually matter, whether you (or your Browser) Requests
the Pages/Pics using BackSlashes or ForwardSlashes! - The Server Sends
them OK.

So - Internet Explorer shouldn't be changing (or has no need to change)
the BackSlashes into Forward Slashes Firefox should be able to get the
Files OK using the BackSlashes, since the Server Sends them OK,
regardless of which sort of Slash is actually used in the Request!

BUT...
I noticed that the HTML Code of the Page has BackSlashes in not only the
<a href="..."> Links to the Pages containing the Pics, but also in the
<img src="..."> Tags for the Thumbnails (on the Index Page) as well!

<quote>
<a href="main\01.htm"><img src="thumb\01.jpg" vspace="5" hspace="5"
width="160" height="120" border="1" alt="strippedCaption"></a>
</quote>

& on the Page "main\01.htm", the HTML says this (for the Main Pic)...

<quote>
<img src="01.jpg" width="1024" height="768" alt="strippedcaption">
</quote>

So if the cause of the prob was the BackSlashes in the URLs, that
Firefox didn't expect/like (though which are actually perfectly
legitimate & should be used/Sent as such), how come it managed to
Fetch the Thumbnails OK then?

& how come it managed to Fetch the "main\01.htm" Page itself, but not
the JPG Pic on that Page?

MCC (& anybody else who might be interested in sussing out the prob),
can you try going to these URLs *Directly* & Posting up (describing)
what the Browser shows in the AddressBar (in other words does it change
the BackSlashes to Forward Slashes? - But bear in mind that even if IE
*shows* BackSlashes in the AddressBar, it actually changes them to
ForwardSlashes, when it Sends the HTTP Request to the Web Server)
& what does it Fetch & what does it actually show?

The Main Index Page...
http://sites.ecosse.net/biffos21/brt/

The First Thumbnail on that Main Index Page (the others are basically
the same)...
http://sites.ecosse.net/biffos21/brt/thumb\01.jpg

The Page that is Linked to from the First Thumbnail on the Index Page...
http://sites.ecosse.net/biffos21/brt/main\01.htm

& the Pic on that Page...
http://sites.ecosse.net/biffos21/brt/main\01.jpg

When we know what happens with them, then we can suss out what is
causing
them not to show up as expected in the Browser, on the normal Page(s).

--
pmj


.

Relevant Pages

  • Re: xhtml style.left problem
    ... Since a few weeks I am trying to use xhtml i.s.o html everywhere in my web ... IE6 but not in Firefox when I use a DOCTYPE ... On the server you have to associate an extension such as .xhtml ...
    (alt.html)
  • Re: How to do a post back when user press enter.
    ... It is hosted on a web server, ... the client browser, which is designed to read and interpret HTML. ... UI, via the event handler. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: PHP-Yes, HTML-No --- Why?
    ... The .html signifies that the file contains HTML - and pretty ... A php script contains both HTML and PHP code so technically speaking it's not just HTML. ... The user is getting a file from your web server, an HTML file, and it has an extension of something other than HTML. ... I hope you weren't configuring them as per your personal likes and dislikes but instead were configuring them as per the customer requirements and for speed, ...
    (comp.lang.php)
  • Re: PHP-Yes, HTML-No --- Why?
    ... You are arguing to have ..html at the end of every URL even if the file contains PHP or another scripting language. ... By that very figure you are in the minority and I'd venture to guess the the number of people who really, really care about such trivial things such as yourself is probably closer to .1% in the real population. ... FTP requests are not HTTP. ... The point about MP3 files is that if you configure your web server to treat every file as potentially having dynamic content and that it should search through the entire file looking to determine exactly which language might be in use in the file and hand it off to the appropriate parser, interpreter or module then you are gonna have to contend with the fact that occasionally you're gonna be charging the web server with reading and parsing potentially huge files - all in the name of a foolish consistency. ...
    (comp.lang.php)
  • Re: How to do a post back when user press enter.
    ... > requested by a client browser, ... > by an ISAPI (Internet Server Application Programming Interface) ... > and interpret HTML. ... > to its process and UI, via the event handler. ...
    (microsoft.public.dotnet.framework.aspnet)