[Bug 29969] Protocol-relative URLs in ResourceLoader (CSSMin)

2011-07-19 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=29969 --- Comment #5 from Roan Kattouw 2011-07-19 22:48:12 UTC --- Strange. I also have $wgServer set to a protocol-relative URL, which will make your wiki explode on 1.17 or lower. Maybe it's that, or maybe something changed. -- Configure bugmail

[Bug 29969] Protocol-relative URLs in ResourceLoader (CSSMin)

2011-07-19 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=29969 --- Comment #4 from Laurence 'GreenReaper' Parry 2011-07-19 21:46:21 UTC --- Not true! $wgStylePath was protocol-relative. $wgExtensionAssetsPath wasn't set at all. I tried setting it and it didn't seem to make any difference (not that I'd exp

[Bug 29969] Protocol-relative URLs in ResourceLoader (CSSMin)

2011-07-19 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=29969 Roan Kattouw changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 29969] Protocol-relative URLs in ResourceLoader (CSSMin)

2011-07-19 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=29969 --- Comment #2 from Roan Kattouw 2011-07-19 20:58:18 UTC --- (In reply to comment #1) > Preferably there would be no need to cache separate HTTP and HTTPS copies, I agree, that's what we're also aiming for for our future WMF HTTPS setup. > or

[Bug 29969] Protocol-relative URLs in ResourceLoader (CSSMin)

2011-07-19 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=29969 --- Comment #1 from Laurence 'GreenReaper' Parry 2011-07-19 20:48:55 UTC --- To provide further insight on caching, my use case is: Apache (serving privately on http port 81) talking to Varnish (serving publicly on port 80) - Squid could be