• Nils Goroll's avatar
    be more specific about the reason for a failed PROXYv2 session · 5764e6c5
    Nils Goroll authored
    We reported any PROXY connection failure as JUNK. Now we report the same
    reasons as for failing HTTP1 connections.
    
    Implmentation:
    
    SES_DeleteHS() asserts that the hs argument be negative (one of
    JUNK, CLOSE, TIMEOUT, OVERFLOW, EOF).
    
    HTC_RxStuff() may return OVERFLOW, JUNK, COMPLETE, EOF or TIMEOUT (or,
    instead of TIMEOUT, IDLE if the callback returned EMPTY).
    
    Because vpx_complete() only returns JUNK, OVERFLOW or MORE, using
    the HTC_RxStuff() return value for SES_DeleteHS() is safe if different
    from COMPLETE.
    5764e6c5
Name
Last commit
Last update
.circleci Loading commit data...
.github Loading commit data...
bin Loading commit data...
doc Loading commit data...
etc Loading commit data...
include Loading commit data...
lib Loading commit data...
m4 Loading commit data...
man Loading commit data...
tools Loading commit data...
.dir-locals.el Loading commit data...
.gitignore Loading commit data...
.lgtm.yml Loading commit data...
.syntastic_c_config Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING Loading commit data...
ChangeLog Loading commit data...
INSTALL Loading commit data...
LICENSE Loading commit data...
Makefile.am Loading commit data...
README.Packaging Loading commit data...
README.rst Loading commit data...
autogen.des Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
flint.lnt Loading commit data...
varnish-legacy.m4 Loading commit data...
varnish.m4 Loading commit data...
varnishapi-uninstalled.pc.in Loading commit data...
varnishapi.pc.in Loading commit data...
vtc.am Loading commit data...