[tor-bugs] #12778 [meek]: Put meek HTTP headers on a diet

[Tor Bug Tracker & Wiki]

#12778: Put meek HTTP headers on a diet
-----------------------------+-----------------
     Reporter:  dcf          |      Owner:  dcf
         Type:  enhancement  |     Status:  new
     Priority:  normal       |  Milestone:
    Component:  meek         |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------

Comment (by dcf):

 [https://gitweb.torproject.org/pluggable-
 transports/meek.git/commitdiff/b1f6a7ece3adaf8a781a5a97877fcf0f20c736a7
 b1f6a7ec] removed Content-Type from meek-client.

 I tried removing Content-Type [https://gitweb.torproject.org/pluggable-
 transports/meek.git/blob/b1f6a7ece3adaf8a781a5a97877fcf0f20c736a7:/firefox/components/main.js#l223
 from the Firefox extension] (passing an empty string for the aContentType
 argument to [https://developer.mozilla.org/en-
 US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIUploadChannel#setUploadStream%28%29
 nsIUploadChannel.setUploadStream], but it didn't work. Apparently setting
 an empty string also prevents the Content-Length header from being added,
 so the POST just hangs forever, at least on www.google.com.

 I didn't try removing it from the Chrome extension.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12778#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online