Require both source and destination to be HTTPS / secure context

privacycg / private-click-measurement

Private Click Measurement

https://privacycg.github.io/private-click-measurement/

196 stars 8 forks source link

Require both source and destination to be HTTPS / secure context #58

Open johannhof opened 3 years ago

johannhof commented 3 years ago

As noted in #30 it might be good to align on whether this feature should be exposed to insecure transport. Apart from the obvious benefit of user privacy and pushing HTTPS forward, there seems to be some room for simplification of the report structure with HTTPS-only.

johannhof commented 3 years ago

Trying to summarize feedback from various vendors and browsers in the Jan 14 meeting, there were no concerns around this proposal as HTTPS seems to be a requirement/default in almost all organizations and their partners. We can probably remove this from the agenda.