summaryrefslogtreecommitdiff
path: root/libpod
diff options
context:
space:
mode:
authorKorhonen Sami (Samlink) <k847259@ubuntu.saminet.fi>2020-07-09 12:09:58 +0300
committerKorhonen Sami (Samlink) <k847259@ubuntu.saminet.fi>2020-07-09 22:16:16 +0300
commit8b07ae32787ce61717b94aa7e5cc6ee02f4efa1d (patch)
treebbd1c5282802c6f9b44c529a241700b848badf1f /libpod
parentcf64e3cad89053e85071760eb911b58739867163 (diff)
downloadpodman-8b07ae32787ce61717b94aa7e5cc6ee02f4efa1d.tar.gz
podman-8b07ae32787ce61717b94aa7e5cc6ee02f4efa1d.tar.bz2
podman-8b07ae32787ce61717b94aa7e5cc6ee02f4efa1d.zip
Fix: Hijacking v2 endpoints to follow rfc 7230 semantics
After this patch v2 hijacking endpoints, exec/start and containers/attach follow rfc 7230 specification. Connection will only be upgraded, if client specifies upgrade headers: For tcp connections: Connection: Upgrade Upgrade: tcp For unix socket connections: Connection: Upgrade Upgrade: sock There are currently no checks if upgrade type actually matches with available protocols. Implementation just protocol that client requested Signed-off-by: Sami Korhonen <skorhone@gmail.com>
Diffstat (limited to 'libpod')
0 files changed, 0 insertions, 0 deletions