Implement a CheckTor API #221
Comments
|
Current specification discussed with @fpietrosanti is the following:
|
evilaliv3
added a commit
that referenced
this issue
Feb 21, 2015
with this commit Tor2web introduces a CheckTor API. Current implementation acts as following: - the API permits requests to a /gettor resource - the resource provide an output compliant to current Tor API implemented at: https://check.torproject.org/api/ip - the HTTP response injects an x-check-tor header returning a simple boolean value depending if the user is detected to be using Tor or not - the resource allows CORS as specified in https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
evilaliv3
added a commit
that referenced
this issue
Feb 21, 2015
with this commit Tor2web introduces a CheckTor API. Current implementation acts as following: - the API permits requests to a /gettor resource - the resource provide an output compliant to current Tor API implemented at: https://check.torproject.org/api/ip - the HTTP response injects an x-check-tor header returning a simple boolean value depending if the user is detected to be using Tor or not - the resource allows CORS as specified in https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
evilaliv3
added a commit
that referenced
this issue
Feb 22, 2015
with this commit Tor2web introduces a CheckTor API. Current implementation acts as following: - the API permits requests to a /gettor resource - the resource provide an output compliant to current Tor API implemented at: https://check.torproject.org/api/ip - the HTTP response injects an x-check-tor header returning a simple boolean value depending if the user is detected to be using Tor or not - the resource allows CORS as specified in https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS Conflicts: tor2web/t2w.py
evilaliv3
added a commit
that referenced
this issue
Feb 22, 2015
with this commit Tor2web introduces a CheckTor API. Current implementation acts as following: - the API permits requests to a /gettor resource - the resource provide an output compliant to current Tor API implemented at: https://check.torproject.org/api/ip - the HTTP response injects an x-check-tor header returning a simple boolean value depending if the user is detected to be using Tor or not - the resource allows CORS as specified in https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
evilaliv3
added a commit
that referenced
this issue
Feb 22, 2015
with this commit Tor2web introduces a CheckTor API. Current implementation acts as following: - the API permits requests to a /gettor resource - the resource provide an output compliant to current Tor API implemented at: https://check.torproject.org/api/ip - the HTTP response injects an x-check-tor header returning a simple boolean value depending if the user is detected to be using Tor or not - the resource allows CORS as specified in https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS Conflicts: tor2web/t2w.py
|
Finalize documentation on the different use-case of Tor2web CheckTor Javascript https://github.com/globaleaks/Tor2web-3.0/wiki/CheckTor |
|
Done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The aim of this ticket is to design and and implement a CheckTor API useful for allowing clients to detect if they are using Tor or not, by simply making requests to a Tor2web domain.
This would allow to perfom this check on the same domain of a Tor2web instance without requiring user to perform requests to different domain, or to implement the check on an existing domain of an initiative without leaking any requests to external services.
The text was updated successfully, but these errors were encountered: