summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Add path selection probabilities to details files.Karsten Loesing2012-07-20
|
* Stop supporting old-style URLs.Karsten Loesing2012-07-17
|
* Stop highlighting news from 1 month ago.Karsten Loesing2012-07-17
|
* Don't escape ' in JSON strings.Karsten Loesing2012-07-06
| | | | Fixes #6309, found by lunar.
* Trivial log message fix.Karsten Loesing2012-07-02
|
* Tweak build file.Karsten Loesing2012-06-19
|
* Try harder not to look up host names repeatedly.Karsten Loesing2012-06-18
|
* Add a DESIGN document.Karsten Loesing2012-06-18
|
* Only include dir_address if dirport != 0.Karsten Loesing2012-06-18
| | | | | Onionoo's protocol specification says "Omitted if the relay does not accept directory connections." Let's do what the spec says.
* Perform reverse DNS lookups to learn relay host names.Karsten Loesing2012-06-18
| | | | Implements #5247.
* Support searches for more than 1 search term.Karsten Loesing2012-06-18
| | | | | | Works only for search=... parameter, not for search/... URLs. Implements #5248.
* Support IPv6 addresses in summary, details, and search.Karsten Loesing2012-06-15
| | | | Implements #5245.
* Fix running bits in summary document.Karsten Loesing2012-06-15
|
* Include exit addresses in summary and search.Karsten Loesing2012-06-15
| | | | Implements #5251.
* Add country parameter to search by country code.Karsten Loesing2012-06-14
| | | | Implements #5960.
* Clean up previous commit a bit.Karsten Loesing2012-06-14
|
* Use more appropriate node summary file in servlet.Karsten Loesing2012-06-14
| | | | | | | We used a JSON-formatted summary document and a .csv file to decide which relays and bridges to return in the servlet. This is overly complex and unnecessary. We have a fine summary file that contains all information we need and that can be easily extended.
* Stop highlighting news from 1 month ago.Karsten Loesing2012-06-14
|
* Improve documentation of bridge nicknames a bit.Karsten Loesing2012-06-14
|
* Fix nickname search for bridges.Karsten Loesing2012-06-14
|
* Fix running field for bridges.Karsten Loesing2012-06-14
| | | | | | | Bridges got the running bit if they were contained in the last known status, regardless of a possibly missing Running flag. This doesn't matter for relays, because all relays in the consensus have the Running flag. That's not true for bridges.
* Include bridge nicknames in documents.Karsten Loesing2012-06-14
|
* Add Eclipse's project files to .gitignore.Karsten Loesing2012-06-14
|
* Don't break when reading a broken history file.Karsten Loesing2012-06-01
|
* Remove announced changes that are more than 1 month old.Karsten Loesing2012-05-14
|
* Changes were not deployed on April 3, but today.Karsten Loesing2012-05-14
|
* Add parameters for filtering and sorting results.Karsten Loesing2012-04-03
| | | | | | | | | | | Parameters are more flexible than our current URLs. Current functionality can be implemented with the type, running, search, and lookup parameters. The order and limit parameters can be used, e.g., for top-10 lists of relays by bandwidth. The offset parameter might be useful for paged results. This is a major API change, so we're leaving the deprecated methods in for two months instead of one.
* A consensus weight of 0 is still valid.Karsten Loesing2012-04-03
|
* Add consensus_weight field to relay details.Karsten Loesing2012-04-03
|
* Add Commons Compress to build path.Karsten Loesing2012-04-03
| | | | This .jar is now required by metrics-lib.
* Stop calling the changes from 1 month ago 'new.'Karsten Loesing2012-04-03
|
* Take out some useless code.Karsten Loesing2012-04-02
| | | | | | All details files with descriptor details now contain a last_restarted field, and if they don't contain descriptor details we won't be able to write a last_restarted line anyway.
* Rename a variable.Karsten Loesing2012-04-02
|
* Don't use server descriptors parse histories.Karsten Loesing2012-04-02
| | | | | | | | If we parse a relay or bridge server descriptor that we never saw before and learn about the relay or bridge in a later consensus or status, we'll never write the descriptor content anywhere. The result would be details files containing no descriptor parts until the relay or bridge publishes the next descriptor. Yes, this took a long time to track down.
* Make Onionoo out/ directory configurable.Karsten Loesing2012-04-02
|
* Allow the webapp to be deployed as onionoo.war.Karsten Loesing2012-04-02
| | | | | | | So far, we assumed that the webapp is deployed as ROOT.war which means URLs are, e.g., /summary/all. Now we allow the webapp to be deployed as onionoo.war which leads to URLs like /onionoo/summary/all. Handle both variants.
* Make sure country codes are lower-case as specified.Karsten Loesing2012-03-23
|
* Accept hashed fingerprints in search and lookup URLs.Karsten Loesing2012-03-19
| | | | | | | | | | | | | | | | | | | | | | | | More precisely, accept hashed relay fingerprints and hashed hashed bridge fingerprints. The problem addressed here is that both */lookup/ and */search/ URLs require a non-hashed fingerprint to look up a relay and a hashed fingerprint to look up a bridge. This works fine if a) users know how to hash fingerprints and b) the client knows whether the user provided a hashed or non-hashed fingerprint. But what if either a) or b) is not the case? If the client sees a 40-character fingerprint it shouldn't simply submit it to the server. It might be a non-hashed bridge fingerprint. The change made here is to make */lookup/ and */search/ URLs accept hashed relay fingerprints and hashed hashed bridge fingerprints. Clients can now be advised to always hash any 40-character hex input they receive from users and include that in their request to the server. If the user provides a non-hashed fingerprint of a bridge the client won't reveal the non-hashed fingerprint in the URL. If the user provides a hashed fingerprint, looking up the hash of the hash still works and returns the bridge the user was looking for. Implements #5368.
* Remove two now unneeded lines.Karsten Loesing2012-03-19
|
* Remove lower-resolution bandwidth data that adds no information.Karsten Loesing2012-03-13
| | | | | | | | | | | From GitHub issue #2: "We include bandwidth data for all time periods as soon as we have at least two data points. But sometimes a time period is completely contained in another, shorter time period, where graphs have a higher resolution. For example, if a relay is only running for a few months, we don't need to include bandwidth data for the 5-years graph, but only for the 1-year graph. In general, we only need to include bandwidth data up to the point where the start of a time period precedes the first bandwidth data point. No need to include larger time periods."
* No need to use an absolute path for the favicon.Karsten Loesing2012-03-13
|
* Add favicon.Karsten Loesing2012-03-12
|
* Implement caching using Last-Modified/If-Modified-Since headers.Karsten Loesing2012-03-09
|
* Exclude votes from rsync.Karsten Loesing2012-03-09
|
* Fix copy-paste bug leading to missing as_name fields.Karsten Loesing2012-03-09
|
* Escape "s in AS names and other fields.Karsten Loesing2012-03-05
|
* Allow for missing server descriptors.Karsten Loesing2012-03-05
|
* Remove deprecated details.Karsten Loesing2012-03-05
|
* Remove version, valid_after, and fresh_until lines from responses.Karsten Loesing2012-03-05
|
* Make protocol page the new index.html.Karsten Loesing2012-02-29
|
generated by cgit v1.2.1 (git 2.18.0) at 2024-02-08 07:42:39 +0000