As part of #30472 (moved), we are setting up a service on polyanthum that allows bridge operators to test the TCP reachability of their obfs4 port. We would like to expose the service over a URL such as bridges.torproject.org/scan/. This seems to require a new ProxyPass directive in the file /etc/apache2/sites-enabled/bridges.torproject.org.conf.
What's the process for modifying this file? Is it under version control? If so, how do we commit a change to this version control system?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
just in case it's only under our control, could you specify exactly the line you want to have added so i can just do it instead of bounce it back to you here later? :)
I think this is what I want. I didn't actually test it because I filed this ticket instead :) Basically, I want requests going to bridges.torproject.org/scan/ to be redirected to another web server that listens on 127.0.0.1:4000.
Those changes were also committed into git, through the daily autocommit. Hilarious. :)
In any case, those files are only writable by root, so I guess you need to ask me or other tpa to make changes.
So I just implemented your change. I grepped through the access log and it seems the /scan prefix wasn't in use anywhere, so it's a safe bet. The thing gives us a 404 right now, but I guess that's to be expected because it doesn't seem like anything is running on port 4000. Here's the error log in apache:
[Fri May 31 00:43:11.833004 2019] [proxy:error] [pid 17339:tid 140323233597184] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:4000 (127.0.0.1) failed
I've committed the change into RCS and git, for good measure.
Then I'll try to forget what I have seen here, for mental health reasons. :p
I hope that helps!
Trac: Status: assigned to closed Resolution: N/Ato fixed
and, and for the record, those are the commands to commit the file:
co -l bridges.torproject.org.conf # unlock the file (ie. make it writable. yes, this is a thing in RCS.)ci -m'... commit message ...' -u bridges.torproject.org.conf # this commits the file, and unlocks itgit commit -m'...commit message...' . # also commit everything into git, including the RCS directory of course
watch out for the ci command. by default, it removes the committed file if you don't use any flags, which might be... surprising, to say the least, for people used to more... modern VCS.