bridgestrap issueshttps://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/issues2021-06-10T19:44:03Zhttps://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/issues/2Make it clear if response was served from cache or not2021-06-10T19:44:03ZPhilipp Winterphw@torproject.orgMake it clear if response was served from cache or not@cohosh [pointed out](https://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/commit/ecc6e0487655af9ab6f91ff4fbab7ce76d11caa7#note_2709958) that it's currently not clear if a given bridge line was cached or not. This is problemat...@cohosh [pointed out](https://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/commit/ecc6e0487655af9ab6f91ff4fbab7ce76d11caa7#note_2709958) that it's currently not clear if a given bridge line was cached or not. This is problematic in an interactive scenario where a bridge operator is trying to fix her bridge, while repeatedly calling bridgestrap. Nobody wants to wait 24 hours until bridgestrap expires your cache entry. We should do the following:
* Make it clear in bridgestrap's JSON response if a given bridge line was cached or not.
* Consider allowing clients to bypass bridgestrap's cache, e.g. by adding a new field to the JSON request.