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

Support HTTP Basic Authentication for API #245

Closed
tilgovi opened this Issue Jan 10, 2013 · 4 comments

Comments

Projects
None yet
4 participants
@tilgovi
Copy link
Contributor

tilgovi commented Jan 10, 2013

No description provided.

@ghost ghost assigned tilgovi Jan 10, 2013

@csillag

This comment has been minimized.

Copy link
Contributor

csillag commented Mar 22, 2013

Explanation (by tilgovi):
This is for developers.
Makes it possible to get an API auth token without having cookies, such as using curl, or any number of HTTP client libraries in any language.

@tilgovi tilgovi removed their assignment Feb 5, 2014

@tilgovi tilgovi removed the steak label Jul 28, 2014

@tilgovi tilgovi removed the 1 - Ready label Oct 7, 2014

@jibe-b

This comment has been minimized.

Copy link

jibe-b commented Nov 23, 2015

This is for users too! I'd love not to have to copy paste in browser (and login cookies) the annotations I made and eventually edit them through HTTP queries.

@jibe-b

This comment has been minimized.

Copy link

jibe-b commented Dec 4, 2015

Here is authentication cookies can be used from cURL, assuming cookies have been exported to cookies.txt (install firefox's export-cookies addon for example)

curl -b cookies.txt http://hypothes.is/api/search?tag=w3c

@nickstenning

This comment has been minimized.

Copy link
Contributor

nickstenning commented Feb 10, 2016

Hi there! I'm going to close this as part of a clean-up of all issues currently open on this repo that represent ideas or features rather than reports of bugs or technical chores.

I want to be clear that this isn't intended to say anything at all about the content of this issue—it certainly doesn't mean we're no longer planning to do the work discussed here—just that we don't want to use GitHub issues to track feature requests or ideas, because the threads can get long and somewhat unwieldy.

If you're interested in what we are working on at the moment, you can check out our Trello board and, for a longer-term view, our roadmap.

And, if you're interested in following up on this issue, please do continue the discussion on our developer community mailing list. You might also want to check out our contributing guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.