On 2/17/06, <b class="gmail_sendername">Jan Erik Moström</b> <<a href="mailto:lists@mostrom.pp.se">lists@mostrom.pp.se</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A question:<br><br>I'm running a pmwiki locally on my powerbook, one thing I've noticed is that<br>if type<br><br> <a href="http://127.0.0.1/~jem/privat">http://127.0.0.1/~jem/privat</a><br><br>then the page will never load, but if I type
<br><br> <a href="http://127.0.0.1/~jem/privat/">http://127.0.0.1/~jem/privat/</a><br><br>then everything works perfectly. What could be the reason?<br></blockquote></div><br>Strictly speaking the above two URLs are referring to completely different things.
<br><br><a href="http://127.0.0.1/~jem/privat">http://127.0.0.1/~jem/privat</a> refers to a *document* called "privat" in the /~jem directory.<br><br><a href="http://127.0.0.1/~jem/privat/">http://127.0.0.1/~jem/privat/
</a> refers to the *directory* "privat" in the /~jem directory and therefore, according to the protocols, a default document within that directory.<br><br>So in your case, having the trailing slash gives expected results and omitting it gets into some crazy loop as it tries to deal with "privat" as a document/script/whatever.
<br><br>My brother uses Macs and some time ago he had a problem with Safari not being able to access my website because I was sending him links without the trailing slash. Once he added the slash, all worked perfectly. I think in total it must be a conversation between the browser and server.
<br><br>Browser: Give me this object<br>Server: Doesn't exist<br>Browser: Give me the default document in this directory<br>Server: Here you go<br><br>My brother's experience suggests that it is definitely the browser that makes the decision between object and directory initially, but I do know that the default documents are defined at the server (as only makes sense).
<br><br>Most browsers other than Safari seem to have this conversation but apparently Safari (or at least some versions) doesn't.<br><br>Hope this helps.<br><br>-- <br>Allister