Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dict-schema URLs show the underlying protocol, not just the result #1809

RalphCorderoy opened this issue Aug 19, 2017 · 2 comments

dict-schema URLs show the underlying protocol, not just the result #1809

RalphCorderoy opened this issue Aug 19, 2017 · 2 comments


Copy link

@RalphCorderoy RalphCorderoy commented Aug 19, 2017

Hi, curl 7.55.1-1 on Arch Linux.

This invocation shows just the data and not the underlying protocol, and
that's what I'd expect.

$ curl -sSL; echo
<html><head><title>Links</title></head><body>0 </body></html>

So why does this one have the `220', etc., clutter?

$ curl -sSL dict://
220 dictd 1.12.1/rf on Linux 4.4.0-1-amd64 <auth.mime> <>
250 ok
150 1 definitions retrieved
151 "yagni" foldoc "The Free On-line Dictionary of Computing (18 March 2015)"
You aren't gonna need it

   <programming> (YAGNI) A motto of {extreme programming} expressing
   the principle that functionality should not be implemented until
   it is needed.  The traditional {waterfall model} makes it
   difficult to add features after the specification has been signed
   off, tempting the specifier to add features that may never be used
   but which take time to program, debug, test and document.


250 ok [d/m/c = 1/0/9; 0.000r 0.000u 0.000s]
221 bye [d/m/c = 0/0/0; 0.000r 0.000u 0.000s]
@bagder bagder added the help wanted label Aug 20, 2017
Copy link

@bagder bagder commented Aug 20, 2017

I can't think of a good reason other than that nobody ever cleaned it up...

Copy link

@RalphCorderoy RalphCorderoy commented Jan 28, 2018

I'm surprised docs/KNOWN_BUGS is more read by potential bug fixers than Github's Issues. Otherwise, it looks like a way to bury bugs and get the Issue-count down. :-) Also, I now have no way of tracking if or when this issue is fixed because it has been prematurely closed. The policy and workflow seem wrong, as if pre-Github.

@lock lock bot locked as resolved and limited conversation to collaborators May 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.