I agree HTTP code IS a wrong idea and nobody will implement that.<br><br>>>* HTTP error codes do provide a computer-readable explanation for what<br>
>>went wrong, but I don't know of any gopher server which provides them<br>
>>and it doesn't seem likely that servers would do so in the future. I'd<br>
>>like to know what the rest of the community thinks about this.<br><br>And... Bitch PLZ it's HTTP !!!!! U FUCKING KIDDING ME ?<br><br>:D<br><br><div class="gmail_quote">2012/6/21 Wolfgang Faust <span dir="ltr"><<a href="mailto:wolfgangmcq@gmail.com" target="_blank">wolfgangmcq@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">* I think that the caps file, about.txt and robots.txt should be in<br>
the standard because many servers use them and there isn't a better<br>
place to define them.<br>
* HTTP error codes do provide a computer-readable explanation for what<br>
went wrong, but I don't know of any gopher server which provides them<br>
and it doesn't seem likely that servers would do so in the future. I'd<br>
like to know what the rest of the community thinks about this.<br>
* The redirect is for clients which don't support URL: links but which<br>
do support HTML. They will be sent to the correct location so that<br>
they're not left wondering what went wrong.<br>
The example redirect is malformed HTML -- I thought I fixed it on the<br>
Google Doc but I can't find the revision anywhere. It seems that it<br>
was mangled by the original email transmission and nobody noticed<br>
(including me) because it looks OK at first glance. The valid HTML is:<br>
<HTML><br>
<HEAD><br>
<META HTTP-EQUIV="refresh" content="2;URL=<a href="http://www.example.com/" target="_blank">http://www.example.com/</a>"><br>
</HEAD><br>
<BODY><br>
You are following an external link to a Web site. You will be<br>
automatically taken to the site shortly. If you do not get sent<br>
there, please click<br>
<A HREF="<a href="http://www.example.com/" target="_blank">http://www.example.com/</a>">here</A> to go to the web site.<br>
<P><br>
The URL linked is:<br>
<P><br>
<A HREF="hhttp://<a href="http://www.example.com/" target="_blank">www.example.com/</a>"><a href="http://www.example.com/" target="_blank">http://www.example.com/</a></A><br>
<P><br>
Thanks for using Gopher!<br>
</BODY><br>
</HTML><br>
<div class="HOEnZb"><div class="h5"><br>
On 6/21/12, Nick Matavka <<a href="mailto:n.theodore.matavka.files@gmail.com">n.theodore.matavka.files@gmail.com</a>> wrote:<br>
> On 21 June 2012 09:28, Damien Carol <<a href="mailto:damien.carol@gmail.com">damien.carol@gmail.com</a>> wrote:<br>
>> I agree, every modern server I saw have "about" node and many have<br>
>> "robots.txt" and "caps.txt".<br>
>><br>
>> I think you should consider writing your document in "RFC" format.<br>
>><br>
>> Many RFC only formalize use of techs like robots.txt.<br>
>><br>
>><br>
>> 2012/6/21 Nick Matavka <<a href="mailto:n.theodore.matavka.files@gmail.com">n.theodore.matavka.files@gmail.com</a>><br>
>>><br>
>>> On 21 June 2012 04:16, Christoph Lohmann <<a href="mailto:20h@r-36.net">20h@r-36.net</a>> wrote:<br>
>>> > Greetings.<br>
>>> ><br>
>>> > On Thu, 21 Jun 2012 10:16:05 +0200 Nick Matavka<br>
>>> > <<a href="mailto:n.theodore.matavka.files@gmail.com">n.theodore.matavka.files@gmail.com</a>> wrote:<br>
>>> >> Hello, world!<br>
>>> >><br>
>>> >> Having spent several weeks writing this, I believe that the draft RFC<br>
>>> >> is just about ready to be published. Without further ado, allow me<br>
>>> >> to<br>
>>> >> present the new Gopher specification! Unless anyone says otherwise,<br>
>>> >> this is what will get published.<br>
>>> >><br>
>>> >> <a href="http://piratepad.net/gopher" target="_blank">http://piratepad.net/gopher</a><br>
>>> >> [snip ... too long signature]<br>
>>> ><br>
>>> > I am against this draft:<br>
>>> > 1.) The caps file shouldn't be in the *protocol* specification.<br>
>>> > 2.) robots.txt shouldn't be in the *protocol* specification.<br>
>>> > 3.) about.txt shouldn't be in the *protocol* specification.<br>
>>> > 4.) The definition of the full stop termination of text files in<br>
>>> > this draft does not solve anything. It can be sent as before<br>
>>> > and clients have to take some magic to know if it is part of<br>
>>> > the content or the transfer protocol.<br>
>>> > 5.) Why is there a need to include the HTTP error codes? Item type<br>
>>> > 3 and predefined strings should simplify it.<br>
>>> > 6.) Who uses this TITLE stuff?<br>
>>> > 7.) According to that draft proposal it is possible to have the<br>
>>> > URL: redirections in every selector. This would create much<br>
>>> > confusion without the »h« item type in conjunction.<br>
>>> > 8.) Servers still have to provide the redirection hack. This draft<br>
>>> > does not solve anything there.<br>
>>> > 9.) Why is there a definition of a redirect page? Why are people<br>
>>> > restricted in it? Couldn't it just be avoided?<br>
>>> ><br>
>>> > My conclusion is, that with that draft in action gopher is nothing<br>
>>> > else<br>
>>> > but a simplified HTTP with hacks and more unspecified behaviour.<br>
>>> ><br>
>>> ><br>
>>> > Sincerely,<br>
>>> ><br>
>>> > Christoph Lohmann<br>
>>> ><br>
>>> ><br>
>>> If caps and robots shouldn't be in the protocol specification, where<br>
>>> does one standardise such things? Several people actually<br>
>>> Google-Doced that these things must be there.<br>
>>><br>
>>> What I am seeking to do is take a snapshot of Gopher as currently<br>
>>> used, and there's no question that caps and robots are currently used.<br>
>>><br>
>>> If I were to implement your changes, there would be nothing left but<br>
>>> effectively the 1991 version of gopher.<br>
>>><br>
><br>
> Mr Carol, just whom do you agree with? Me or Mr Lohmann?<br>
><br>
> --<br>
> /^\/^\<br>
> \----|<br>
> _---'---~~~~-_<br>
> ~~~|~~L~|~~~~<br>
> (/_ /~~--<br>
> \~ \ / /~<br>
> __~\ ~ / ~~----,<br>
> \ | | / \<br>
> /| |/ | |<br>
> | | | o o /~ |<br>
> _-~_ | || \ /<br>
> (// )) | o o \\---'<br>
> //_- | | \<br>
> // |____|\______\__\<br>
> ~ | / | |<br>
> |_ / \ _|<br>
> /~___| /____\<br>
><br>
> _______________________________________________<br>
> Gopher-Project mailing list<br>
> <a href="mailto:Gopher-Project@lists.alioth.debian.org">Gopher-Project@lists.alioth.debian.org</a><br>
> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project</a><br>
><br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
01010111 01101111 01101100 01100110<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Gopher-Project mailing list<br>
<a href="mailto:Gopher-Project@lists.alioth.debian.org">Gopher-Project@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Damien CAROL<br>
<a href="gopher://dams.zapto.org/1/" target="_blank">gopher://dams.zapto.org/1/</a><br>