-
I've read the [estimated timeline](https://github.com/WICG/dbsc/wiki/DBSC-timeline), and looked at the flags available in Chrome Canary 125 on Mac. These don't line up - the estimated timeline suggest…
-
### Description
Request header `sec-ch-ua-mobile":"?0` used in MS Edge triggers false positive on Paranoia Level 4. This header is not present in browsers such as Firefox.
This is a valid heade…
-
## Bug description
Whitespaces in header values are removed by default, with no apparent way to preserve the original header values
Tracing an http request in API Management Service shows in `a…
-
JWS algorithms are case-sensitive, per the JWS/JWA specs[1], and DBSC should consistently use the defined ones `ES256` and `RS256` (rather than `es256` and `rs256` that currently sometimes are used). …
bc-pi updated
5 months ago
-
The section on I-JSON notes serialization concerns about 64-bit numbers that might be required for protocols like QUIC or HTTP/3.
It then says:
> Concretely, the following definition of uint64 s…
-
It's not a mandated requirement, but new fields are encouraged to use Structured Fields --
https://httpwg.org/specs/rfc8941.html
This has a number of advantages:
- well-specified parsing and …
mnot updated
12 months ago
-
This website https://github.com/WICG/ua-client-hints mentions:
```
The Sec-CH-UA-Form-Factor header field represents the form-factor of a device, historically represented as a token in the User-Age…
-
# Internet AD comments for draft-ietf-httpbis-alias-proxy-status-05
CC @ekline
* comment syntax:
- https://github.com/mnot/ietf-comments/blob/main/format.md
* "Handling Ballot Positions":
-…
-
## Problem
Currently checking the number of affected resources for a request is tied to the `application/vnd.pgrst.object+json` media type and it only checks for a value of 1.
## Solution
N…
-
We need a way to test parsers that support sf-date.
How to do that depends a bit on how the "migration" to the new, extended format is to happen. Do we just expect everybody to adopt the new format…