On 8/13/10 2:25 PM, Ray_Net wrote: > Jay Garcia wrote: >> On 13.08.2010 11:11, Ray_Net wrote: >> >> --- Original Message --- >> >>> Stanimir Stamenkov wrote: >>>> Thu, 12 Aug 2010 23:32:34 +0200, /Ray_Net/: >>>>> Stanimir Stamenkov wrote: >>>>> >>>>>> The problem with the non-standard compliant behavior of IE in this case >>>>>> is the URI may contain \ (back-slash) as non-hierarchical separator, >>>>>> therefore IE will incorrectly transform it to a forward slash and >>>>>> result >>>>>> in a non-existent URI. So SeaMonkey's behavior is just fine - not being >>>>>> "clever" about incorrect URIs containing back-slashes instead of >>>>>> forward >>>>>> slashes for hierarchical path separators. >>>>> >>>>> So you said that SM is not clever enough to transform it to a forward >>>>> slash ? >>>> >>>> No, I said: "SM is not 'clever' about", which was meant as "SM is not >>>> stupid to". Sorry for not being clear enough. >>>> >>>>> You are wrong because when i propose to SM the following: >>>>> file:///C:/Program Files/Abyss Web Server/htdocs/IMAGES\pose-yoga.jpg >>>>> he shows me the picture and modify his URL-adress-zone as follow: >>>>> file:///C:/Program Files/Abyss Web Server/htdocs/IMAGES/pose-yoga.jpg >>>>> >>>>> Why SM is clever with file adress and not with webserver adress ? >>>> >>>> I think David E. Ross has given you a very probable explanation in >>>> another reply: >>>> >>>> news://news.mozilla.org:119/[email protected] >>>> >>>> If you want to find out for real, you could ask the Mozilla devs in a >>>> more technical group. >>>> >>> I will not go further, because SM gurus and devs think they are the best >>> ... it's abnormal that SM works in every possible way except when the >>> page is on my isp web space. This was causing me lot of understandings >>> why it did not work when uploaded for "online" general use. >> >> File structure on the local system follows the rules of the particular >> OS involved whereas on a "server", the convention in most cases is quite >> different and therefore interpreted differently by the browser. >> >> file:/server/directory/file.htm is server based >> file:/c:/directory/file.htm is local system based and the browser will >> automatically insert two more // such as: >> >> file:///c:/directory/file.htm >> >> Your image is displayed because everything following the file:/// is >> interpreted as being formatted locally and local rules apply, therefore >> the backslash \ is rendered correctly. >> >> If you try: http://your_server/directory/images\image.jpg will usually >> not work because the \ is an illegal character as such in some browsers >> but not all browsers. IE guesses that the \ is really a / and will work. >> > As explained before http://localhost/IMAGES\pose-yoga.jpg with SM works > ... localhost is a an access to "your_server" (mine)
As explained before, \ is indeed proper for a URI pointing to a LOCAL file. Yes, it works with SeaMonkey. As explained before, \ is improper for a URI pointing to a file on an external host. It does not work with SeaMonkey because it is not a proper character in a URI. RFC 3986 clearly indicates that URIs that give paths to files use / and not \. SeaMonkey complies with that specification; IE does not. Thus, IE is broken and SeaMonkey is correct. -- David E. Ross <http://www.rossde.com/>. Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
