Mercurial > hg > nginx
view src/core/ngx_bpf.h @ 8794:ba5977b38b2e quic
HTTP/3: reordered H3_MISSING_SETTINGS and H3_FRAME_UNEXPECTED.
The quic-http-34 is ambiguous as to what error should be generated for the
first frame in control stream:
Each side MUST initiate a single control stream at the beginning of
the connection and send its SETTINGS frame as the first frame on this
stream. If the first frame of the control stream is any other frame
type, this MUST be treated as a connection error of type
H3_MISSING_SETTINGS.
If a DATA frame is received on a control stream, the recipient MUST
respond with a connection error of type H3_FRAME_UNEXPECTED.
If a HEADERS frame is received on a control stream, the recipient MUST
respond with a connection error of type H3_FRAME_UNEXPECTED.
Previously, H3_FRAME_UNEXPECTED had priority, but now H3_MISSING_SETTINGS has.
The arguments in the spec sound more compelling for H3_MISSING_SETTINGS.
author | Roman Arutyunyan <arut@nginx.com> |
---|---|
date | Fri, 11 Jun 2021 10:56:51 +0300 |
parents | d3747ba486e7 |
children |
line wrap: on
line source
/* * Copyright (C) Nginx, Inc. */ #ifndef _NGX_BPF_H_INCLUDED_ #define _NGX_BPF_H_INCLUDED_ #include <ngx_config.h> #include <ngx_core.h> #include <linux/bpf.h> typedef struct { char *name; int offset; } ngx_bpf_reloc_t; typedef struct { char *license; enum bpf_prog_type type; struct bpf_insn *ins; size_t nins; ngx_bpf_reloc_t *relocs; size_t nrelocs; } ngx_bpf_program_t; void ngx_bpf_program_link(ngx_bpf_program_t *program, const char *symbol, int fd); int ngx_bpf_load_program(ngx_log_t *log, ngx_bpf_program_t *program); int ngx_bpf_map_create(ngx_log_t *log, enum bpf_map_type type, int key_size, int value_size, int max_entries, uint32_t map_flags); int ngx_bpf_map_update(int fd, const void *key, const void *value, uint64_t flags); int ngx_bpf_map_delete(int fd, const void *key); int ngx_bpf_map_lookup(int fd, const void *key, void *value); #endif /* _NGX_BPF_H_INCLUDED_ */