How feasible would it be to port the current trunk https.js to the 1.9.0 branch? Looking at the HG log, there are quite a few changes that are only on trunk. The main patch I'm interested in is bug 462864's, since the test for bug 471962 depends on it.

It should be pretty feasible, if tedious, to wrap up all the changesets (and associated tests, but excluding changes made which weren't intended to change or ensure server correctness) since then into a patch that would apply to 190. Nothing's been added as far as I can remember that depends on stuff which might have changed on trunk. Mostly it'd be fun of disentangling exactly the desired parts of things like bug 428009 or bug 398185 from the extraneous ones. It might be worthwhile, but I doubt I'd be likely to find the time or energy to do it, too many other things to worry about in 191 or on trunk.

(In reply to comment #1) > Mostly it'd be fun of disentangling exactly the desired parts of things like > bug 428009 or bug 398185 from the extraneous ones. Is that really necessary? If there are no trunk-only dependencies, is there any reason not to just port over *all* changes?

Feel free to give it a try; I speculate it won't be that simple, but I could be wrong.

1.9.0 is dead, so's this bug.