file:/ vs file://<host>/ vs file:///

Daniel Veillard veillard at
Thu Nov 4 23:16:25 EET 2004

On Thu, Nov 04, 2004 at 01:32:29PM -0500, Avery Pennarun wrote:
> >   do like Mozilla does file:///etc/hosts , like 2396 suggests
> Mozilla accepts file:/etc/hosts as valid input.

  Sorry you lose credibility there !

  It immediately transforms it to the proper form file:///etc/hosts
This is a "workaround broken user input in the text field" like
it accepts "" but will immediately "correct" it to 
"". So following your point
should also allows an hostname directly, because after all 
everybody knows that it means http://$hostname/

  I persist and maintain that you are seriously confused. That
broken user input should be dealt with sometimes and corrected
but this is *NOT* a reason to allow broken and unspecified
behaviour to enter specs. 

  Now if you *REALLY* believe what you are saying, go work on
an IETF draft for the "file" protocol, that is immensely needed,
but bypassing specs by putting workaround in other specs higher
in the stack is seriously *WRONG*. Don't do this ! You may think
it's easier to push this at the level, this is
however not the right place, and the best way to screw up fd.o 
effort in that direction and loose credibility as soon as more
standard aware people will look at it.


Daniel Veillard      | Red Hat Desktop team
veillard at  | libxml GNOME XML XSLT toolkit | Rpmfind RPM search engine

More information about the xdg mailing list