[tor-bugs] #5168 [TorStatus]: TorStatusBeta, Improve error messages and make clear which data will be accepted

[Tor Bug Tracker & Wiki]

#5168: TorStatusBeta, Improve error messages and make clear which data will be
accepted
----------------------------+-----------------------------------------------
    Reporter:  bastik       |       Owner:        
        Type:  enhancement  |      Status:  closed
    Priority:  normal       |   Milestone:        
   Component:  TorStatus    |     Version:        
  Resolution:  invalid      |    Keywords:        
      Parent:               |      Points:        
Actualpoints:               |  
----------------------------+-----------------------------------------------
Changes (by karsten):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 Replying to [comment:1 bastik]:
 >     http://hellais.github.com/TorStatus/
 >
 >     No JavaScript.
 >     - No content is seen, beside the black bar (top) and the footer (The
 Tor Project - 2012) which appears at the top.
 >     - Search has no function
 >
 >     JavaScript for github.com
 >     - Content is shown, footer is under the content
 >     - Search returns "Backend error!
 >     The backend server replied with an error to your query. This
 probably means that you did not properly format your query. Or that you
 just are trying to fuzz my web app hoping to pwn me. Good luck! ;)"
 >
 >     JavaScript for github and datasource, no external resources are
 allowed to load
 >     - Content is shown
 >     - Search returns "Backend error!
 >     The backend server replied with an error to your query. This
 probably means that you did not properly format your query. Or that you
 just are trying to fuzz my web app hoping to pwn me. Good luck! ;)"
 >
 >     JavaScript for github and datasource, no restriction of external
 sources (or datasource can be accessed)
 >     - Content is shown, footer is under content
 >     - Search works (looks pretty cool, and the results even cooler)

 Good point.  There's no way how Tor Status Beta would work without
 JavaScript, but it could at least tell you that.  I can't comment on the
 various scenarios you describe.  If this is a problem with Tor Status
 Beta, Arturo can probably comment on it.  If it's a problem with the
 backend, I'd like to know what's required to fix it.

 I opened a new issue for this on GitHub, where the Tor Status Beta code is
 actually hosted:

 https://github.com/hellais/TorStatus/issues/7

 If you think it's a problem with the backend, please open a ticket in
 Onionoo's issue tracker:

 https://github.com/kloesing/Onionoo/issues

 >     Notes:
 >     - Seraching for names worked fine (at least I did not saw a problem
 here)
 >     - Seraching for fingerprint results in "Backend error! (...)", if
 the "$" is included. (copied from Vidalia)

 Interesting.  I opened a ticket for that in Onionoo's issue tracker.  I'm
 not sure how Tomcat likes a "$" in the URL (at least it doesn't like
 spaces in URLs, so I wouldn't be surprised).  If the backend cannot solve
 this, the frontend should remove the "$" when searching for a fingerprint.

 https://github.com/kloesing/Onionoo/issues/10

 >     - Searching for vaild fingerprint works.
 >     - Seraching for not existing fingerprint/name returns "No Results
 found!" (good, no error)
 >     - Searching for IPv4 addresses returns a result for relays
 >     - Searching for IPv4:Port returns "Backend error!" (...)

 Right.  Supporting searches for ip:port sounds like a new feature to me.
 Added a new issue for this:

 https://github.com/kloesing/Onionoo/issues/11

 >     It's unclear what I need to know of a bridge to find it.
 >     I loaded http://85.214.195.203/details/running and looked for
 >     - hashed fingerprint: "No Results found!" (I used one that was
 provided)

 Right.  There's already an issue for that:

 https://github.com/hellais/TorStatus/issues/6

 >     - IP adress: "No Results found!" (I used one that was provided)

 That cannot work, because bridge IP addresses are not contained in the
 data that the backend has.  If you think that should be better documented
 somewhere, please let us know.

 > I got advised to copy it here.

 That's good in so far as I found it.  Thank you very much for your report!

 In the future, the better place would be to submit things in the GitHub
 issue trackers.  We didn't turn Tor Status Beta and Onionoo into Tor
 projects yet, which is why Tor's Trac is the wrong place to submit issues.
 That might change in the future.  But right now, GitHub is the right
 place.

 Closing this ticket as invalid (due to lack of a better reason).  All
 issues have been moved to GitHub.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5168#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online