1215235 - Drop support for jar: URIs by default

Status: RESOLVED WONTFIX

(Core :: Networking, defect)

Description

[(no longer active)]

The discussion is happening on dev-platform, this bug tracks the implementation.

Comment 1

[[:fabrice] Fabrice Desré]

Just make sure that you don't break app: at the same time since it's jar:file: in disguise.

Comment 2

[Kohei Yoshino]

Posted the site compatibility doc: https://www.fxsitecompat.com/en-US/docs/2015/jar-protocol-support-will-be-removed/

Comment 3

[Andrea Marchesini [:baku]]

Attachment: jar.patch

Comment 4

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 8682618 [details] [diff] [review]
jar.patch

r=me

Comment 5

[Andrea Marchesini [:baku]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/f38885365d1a

Comment 6

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/f38885365d1a

Comment 7

[Kohei Yoshino]

Posted the site compatibility doc: https://www.fxsitecompat.com/en-US/docs/2015/jar-protocol-support-has-been-disabled-by-default/

Comment 8

[Eric Shepherd [:sheppy]]

Updated https://developer.mozilla.org/en-US/docs/Mozilla/Security/Security_and_the_jar_protocol (which is also moved from its old top-of-site URL) and listed on https://developer.mozilla.org/en-US/Firefox/Releases/45.

Comment 9

[chris hofmann]

for easier reference here is the link to the dev.platform discussion

https://groups.google.com/forum/#!searchin/mozilla.dev.platform/$20jar$3A$20URIs/mozilla.dev.platform/CFd4w8GzdEI/0DDE_cF8BAAJ

Eric, is there a place on MDN (or could their be) that lists out all the upcoming things we might do, or plan to do, that have the possibility of braking web compat or that we know for sure that will?

Getting more web dev's and app developers to look at this kind of centralize resource page, and helping them a way to find their way to the appropriate discussion, and understanding the upcoming schedule for compat breaking changes might be a way of avoiding discovery of incompatibilities *after* we ship and help in the timing and staging of changes like this one.

Comment 10

[Kohei Yoshino]

(In reply to chris hofmann from comment #9)
> Eric, is there a place on MDN (or could their be) that lists out all the
> upcoming things we might do, or plan to do, that have the possibility of
> braking web compat or that we know for sure that will?

That's exactly what I'm working on: https://www.fxsitecompat.com/en-CA/versions/future/

Comment 11

[Kohei Yoshino]

Updating the flags as per Bug 1255139.

Comment 12

[Kohei Yoshino]

Updating the flags again. We should probably try this again with Firefox 53, given that 52 will be the next ESR.

Comment 13

[Kohei Yoshino]

Given IBM fixed their iNotes issue in May and enterprise users will/should be using Firefox 52 ESR, Firefox 53 shipping in April 2017 could be the new target.

Comment 14

[(no longer active)]

Kohei, please don't reopen bugs that have patches landed.  If you want to reopen the discussion to drop remote jar: URIs again, please file a new bug.

Also note that the telemetry probe which we have for this <https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2016-10-19&keys=__none__!__none__!__none__&max_channel_version=release%252F49&measure=REMOTE_JAR_PROTOCOL_USED&min_channel_version=release%252F47&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-09-16&table=0&trim=1&use_submission_date=0> still shows users hitting this in the wild, we will not consider removing this again at this point before that probe drops down to about 0.

Comment 15

[Kohei Yoshino]

The patch here has been backed out in Bug 1255139, so this bug should still be open I guess...?

Comment 16

[Daniel Veditz [:dveditz]]

See bug 1329336 for a new attempt at making this change.