Re: [tor-bugs] #18141 [meek]: Tame "reading from ORPort" error logs in meek-server

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#18141: Tame "reading from ORPort" error logs in meek-server
-------------------------+---------------------
 Reporter:  dcf          |          Owner:  dcf
     Type:  enhancement  |         Status:  new
 Priority:  Medium       |      Milestone:
Component:  meek         |        Version:
 Severity:  Normal       |     Resolution:
 Keywords:               |  Actual Points:
Parent ID:               |         Points:
  Sponsor:               |
-------------------------+---------------------

Comment (by dcf):

 Replying to [comment:3 yawning]:
 > Replying to [comment:1 dcf]:
 > > One possible approach: have client indicate in their HTTP requests
 whether they intend to start a new session with a new session ID. meek-
 server would drop requests with an unknown session ID that don't have this
 bit set, and would request the bit to be not set for any existing session
 ID. That way we would drop the client connection before it gets passed
 through to tor.
 >
 > Hm. Won't this break backwards compatibility?

 No; we'll fall back to the previous behavior if clients don't send
 whatever header has the flag in it (treat it as true/false/null). I think
 we're going to have to add a header with flags for #12857 anyway.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18141#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs