Open Bug 1456088 Opened 6 years ago Updated 3 months ago

Consider to remove nsIURISetters::SetScheme

Categories

(Core :: Networking, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: smaug, Unassigned)

References

Details

(Whiteboard: [necko-triaged])

SetScheme isn't really safe to use, since it just modifies the uri object but doesn't go through protocol handlers.
So for example DOM's URL implementation needs to be careful to not use that, but explicitly create a new nsIURI (which requires use of main thread).

https://searchfox.org/mozilla-central/rev/fcd5cb3515d0e06592bba42e378f1b9518497e3d/netwerk/base/nsIURIMutator.idl#183

If SetScheme is needed for things like http -> https, better to have explicitly a method doing such change which is safe on any thread.
Valentin, can you take this bug?
Flags: needinfo?(valentin.gosu)
Priority: -- → P3
Whiteboard: [necko-triaged]
Yes, of course. I forgot to assign it to myself.
Assignee: nobody → valentin.gosu
Flags: needinfo?(valentin.gosu)

Hey @valentin !
Can I take this up ?
And Can you elaborate this more ?
Thanks :)

Assignee: valentin.gosu → nobody
Severity: normal → S3
See Also: → 1876483
You need to log in before you can comment on or make changes to this bug.