Open Bug 1645116 Opened 5 years ago Updated 5 years ago

Support for Mercure Protocol in SSE Inspector

Categories

(DevTools :: Netmonitor, enhancement, P3)

Product:
DevTools
Component:
Netmonitor
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: farooqbckk, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0

Steps to reproduce:

Mercure Protocol: https://datatracker.ietf.org/doc/draft-dunglas-mercure/
More details: https://twitter.com/dunglas/status/1270635704067018752

Blocks: netmonitor-sse-inspector
Severity: -- → S3
Component: Untriaged → Netmonitor
Priority: -- → P3
Product: Firefox → DevTools
Status: UNCONFIRMED → NEW
Ever confirmed: true

The above tweet mentions showing JWT token and mercure topics in the sse inspector.

  • JWT token is sent as Authorization header so it can viewed in the Headers Panel.
  • Last-Event-ID (standard EventSource header, not related to mercure in particular) is also visible in Headers panel (request headers).
  • Topics are sent as query parameters so they are visible in Requests Panel.
  • Normal updates are sent through data field of event-stream, which are already shown in messages list in Data column.

We will have to see which info(s) is most relevant to be shown in sse tab as well.

Farooq, do we have a test page we could load to see the Mercure protocol in action?

Honza

Flags: needinfo?(farooqbckk)

Yes we do: https://demo.mercure.rocks/

Flags: needinfo?(farooqbckk)
You need to log in before you can comment on or make changes to this bug.