Tor2web
Tor2web copied to clipboard
tor2web
added support for more HTTP response headers
For example, the "Link" and "X-Pingback" headers on: http://54ogum7gwxhtgiya.onion
This patch makes those headers (and others) work as intended.
Correction, URL is: http://54ogum7gwxhtgiya.onion/blog/index.php/welcome-home/
Code quality remained the same when pulling 34fede7 on virgil:patch-38 into 52c7249 on globaleaks:master.
Code quality remained the same when pulling 34fede7 on virgil:patch-38 into 52c7249 on globaleaks:master.
Repository health decreased by 11% when pulling 34fede7 on virgil:patch-38 into 24bbce7 on globaleaks:master.
- 29 new problems were found (including 21 errors and 6 code smells).
- 4 problems were fixed (including 0 errors and 3 code smells).
Repository health decreased by 12% when pulling 34fede7 on virgil:patch-38 into c99a6a9 on globaleaks:master.
- 62 new problems were found (including 22 errors and 37 code smells).
- 8 problems were fixed (including 2 errors and 4 code smells).
Repository health decreased by 17% when pulling 34fede7 on virgil:patch-38 into 85e0f4e on globaleaks:master.
- 60 new problems were found (including 22 errors and 36 code smells).
- 4 problems were fixed (including 0 errors and 3 code smells).
Still think this patch is a good idea. Make more edge cases work. And making edge cases work is nice.
@virgil could you please clarify me the patch?
this way i can validate it and integrate in a release
The important lines are 1087 and 1088. In short, they say, "If we encounter a header we don't recognize, go ahead and do regex URL replacement on it."
I'm presuming that in general if you a .onion URL in a header, it should, by default, be rewritten.