[happy] Re: previous work on reporting

[Valentin Gosu <[e-mail]>]

On Mon, 20 Jul 2026 at 15:54, Erik Nygren <[e-mail]> wrote:

> Bumping this thread, it would be great if browsers could include the HTTP
> version used in webRequest so that IPvFoo (and similar extensions) could
> expose if h1/h2/h3 was used.  Perhaps as an "alpn" attribute for which ALPN
> was negotiated for the connect and is being used for the request?
>

I filed a bug to get this into Firefox:
https://bugzilla.mozilla.org/show_bug.cgi?id=2056277
I'd also point to webrequest.SecurityInfo which exposes a protocolVersion,
but unfortunately it's the TLS protocol version :(
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/SecurityInfo


>
> I've found IPvFoo to be super-useful for seeing how existing HE behaviors
> (and site IPv4/IPv6) service availabilty and connectivity are working in
> practice.
>
> Alternatively, this could be one path for exposing some of the HE
> reporting data model we come up with (such as what is proposed in Mirja's
> qlog draft, or in other variants.)
>
>     Erik
>
>
>
> On Tue, Apr 29, 2025 at 11:17 PM Paul Marks <paul=
> [e-mail]> wrote:
>
>> On Fri, Apr 25, 2025 at 6:32 AM Tim Chown <Tim.Chown=
>> [e-mail]> wrote:
>>
>>> Hi Paul,
>>>
>>>
>>>
>>> On 24/04/2025, 20:44, "Michael Richardson" <[e-mail]>
>>> wrote:
>>>
>>>
>>>
>>> Paul Marks <paul=[e-mail]> wrote:
>>>
>>>     > On 27 March 2025, "Tim Chown" <[e-mail]> wrote:
>>>
>>>     >> I see IPvFoo is still actively developed
>>>
>>>
>>>
>>>     > Hi, I was just browsing the list archives and saw you mention my
>>> extension.
>>>
>>>
>>>
>>>     > Currently IPvFoo gets its information from the webRequest API:
>>>
>>>
>>>
>>>     >
>>> https://developer.chrome.com/docs/extensions/reference/api/webRequest#event-onResponseStarted
>>>
>>>     -> "ip - string optional - The server IP address that the request was
>>>
>>>     > actually sent to."
>>>
>>>
>>>
>>>     > If the WG can persuade Chrome/Firefox to provide concise happiness
>>>
>>>     > information alongside that IP address, then I'll figure out a way
>>> to
>>>
>>>     > present it in IPvFoo.
>>>
>>>
>>>
>>> That's brilliant.
>>>
>>> I want that in IPvFoo.
>>>
>>>
>>>
>>> That’s really good news, thank you.  The reporting aspect of HEv3 is a
>>> ‘side’ activity for the WG, but we’ll certainly remember this offer.
>>>
>>>
>>>
>>
>> This may be a tall ask, but if we have Chrome developers on board, then
>> it would be very useful if happiness-reporting extensions could function
>> without the "Read and Change all your data on all websites" <all_urls>
>> permission.
>>
>> IPvFoo currently has unlimited access to user data, and it is my
>> responsibility to not touch anything sensitive.  I would rather use a
>> hypothetical "network diagnostics" permission that only provides URLs
>> truncated to "protocol://domain", server IP, HTTP version, and similar
>> protocol-level information.  No headers, content scripts, or full URLs.
>> This shouldn't require a new API, just a filter applied to the existing
>> webRequest/webNavigation APIs.
>> _______________________________________________
>> happy mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>>
> _______________________________________________
> happy mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>