Commit Graph

7 Commits

Author SHA1 Message Date
Tatsuhiro Tsujikawa 2afc50bf49 shrpx: Specify long enough timeout to emulate removing timeout
It seems that specifying NULL to bufferevent_set_timeouts() does not
remove timeout, which is described in bufferevent book (but it is not
described in header). As a workaround, we specify long enough timeout
to emulate removing timeout.
2012-07-16 18:42:42 +09:00
Tatsuhiro Tsujikawa 06ed17ff26 shrpx: fixed timeout change is not triggered when tunneling.
For upstream timeout, it seems OpenSSL backed bufferevent does not
remove timeout. Set large timeout as a workaround.
2012-07-14 21:47:28 +09:00
Tatsuhiro Tsujikawa 2c5f40b175 Added SPDY proxy mode.
To enable SPDY proxy, use --spdy-proxy option.  At time of this
writing, the only browser which supports SSL/SPDY proxy is Chrome.

Removed Location and Host header field rewrite.
2012-07-11 16:20:16 +09:00
Tatsuhiro Tsujikawa eb9458bba9 Adjust read/write timeout depending on the request/response state 2012-06-12 23:02:01 +09:00
Tatsuhiro Tsujikawa 6702d34651 Enable EV_READ for downstream connection.
Removed Downstream::force_resume_read() calls.  Added missing delete
downstream in shrpx_spdy_upstream.cc.  In on_stream_close_callback,
delete downstream even if response state != MSG_COMPLETE. This may
cause segmentaiton fault.
2012-06-12 21:56:41 +09:00
Tatsuhiro Tsujikawa e871768d84 Disable read for downstream by default to avoid timeout before request 2012-06-10 01:46:33 +09:00
Tatsuhiro Tsujikawa 9d19e2bfe9 Rewrite connection pooling 2012-06-09 23:14:00 +09:00