- From: Andreas Radinger <andreas.radinger@ebusiness-unibw.org>
- Date: Fri, 06 Jan 2012 12:21:42 +0100
- To: Henry Story <henry.story@bblfish.net>
- CC: Jürgen Jakobitsch <j.jakobitsch@semantic-web.at>, "public-xg-webid@w3.org XG" <public-xg-webid@w3.org>
On 1/6/12 1:53 AM, Henry Story wrote: > On 6 Jan 2012, at 01:46, Jürgen Jakobitsch wrote: > >> hi again, >> >> the file is simply ok and available. >> >> when using telnet you might want to stick to the examples from this page [1] >> >> i'm not a telnet pro, but i get at least my index page without hash, i'm pretty >> sure telnet is able to work with hash uris. > Telnet knows nothing of HTTP. It's just a simple tcp connection. You can use that if you want > to see exactly what is going on the wire. > > Anyway, I am told that sending a URI with a # is a mistake, and that servers are in their right > to send a 404. I suppose I was expecting the apache library to do the right thing by itself. > Hi Henry, you are right, the mistake is the client application which sends a URI with a hash fragment in the HTTP request to a server. => the file is ok => the tomcat server is ok to send a 404 => telnet is a good example of a bad client application Best, Andreas
Received on Friday, 6 January 2012 11:25:08 UTC