You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am embedding pages from cppreference in an iframe from a web app (the jupyter notebook), which fetches the resources from cppreference based on some tag file.
The problem is that when the connection to jupyter is https, the CORS setting disallow loading content from an insecure source. Would it be possible for cppreference to be served over https?
@SylvainCorlay Seems like nothing has been done about serving cppreference over https huh? Did you find any other fix ? I am running jupyterhub over https for my uni.
There has been some discussion with @natekohl and @yuvipanda about how to fix this and configure the old version of mediawiki used by cppreference, but no solution to the issue yet unfortunately.
Regarding your use at your Uni, are you using xeus-cling for C++?
Would upgrading MediaWiki to newer version make https support easier? Upgrading will need code changes to the skins though, I have most of that done some time ago, but it's not tested properly yet.
@povilas -- I suspect upgrading MediaWiki would help make https easier, but
I'm not entirely sure. I think you're right about needing code changes to
the skins, though -- I tried upgrading a few weeks ago and everything kinda
broke. :P
Do you happen to know what kind of code changes the skins would need?
hm, touching the file that defines $wgCacheEpoch seems to have only
partially worked. I wonder if there is a race between HTTP and HTTPS
traffic to get into the cache or something...
On Wed, Mar 28, 2018 at 6:19 PM Nate Kohl ***@***.***> wrote:
I just purged the global cache; in theory, all pages should be re-created
as they are visited now.
On Wed, Mar 28, 2018 at 6:18 PM Sylvain Corlay ***@***.***>
wrote:
> This seems to work, but we still need to do ?action=purge on each new
> page (I just did it on the front page).
> Can it be done globally?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#49 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA1buXIDF9HuG1S3BNnAx6Ma5uce635gks5tjAw2gaJpZM4PRqYe>
> .
>
@natekohl I think you can just delete the en, de, etc. directories within the cache directory - that's where all the html files reside. Be sure not to delete .htaccess accidentally :-)
On Wed, Mar 28, 2018 at 6:27 PM Nate Kohl ***@***.***> wrote:
hm, touching the file that defines $wgCacheEpoch seems to have only
partially worked. I wonder if there is a race between HTTP and HTTPS
traffic to get into the cache or something...
On Wed, Mar 28, 2018 at 6:19 PM Nate Kohl ***@***.***> wrote:
> I just purged the global cache; in theory, all pages should be re-created
> as they are visited now.
>
> On Wed, Mar 28, 2018 at 6:18 PM Sylvain Corlay ***@***.***>
> wrote:
>
>> This seems to work, but we still need to do ?action=purge on each new
>> page (I just did it on the front page).
>> Can it be done globally?
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub
>> <#49 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AA1buXIDF9HuG1S3BNnAx6Ma5uce635gks5tjAw2gaJpZM4PRqYe>
>> .
>>
>
I tried deleting the cache/ and was...somewhat...successful. Parts of it
weren't deletable, presumably because they were being concurrently written
to by MediaWiki.
A more thorough delete of the cache didn't seem to help. Pages loaded via
HTTPS still try to load HTTP stylesheets, until ?action=purge is appended,
after which they correctly load HTTPS stylesheets.
On Wed, Mar 28, 2018 at 6:50 PM Nate Kohl ***@***.***> wrote:
I tried deleting the cache/ and was...somewhat...successful. Parts of it
weren't deletable, presumably because they were being concurrently written
to by MediaWiki.
On Wed, Mar 28, 2018 at 6:31 PM Povilas Kanapickas <
***@***.***> wrote:
> @natekohl <https://github.com/natekohl> I think you can just delete the
> directories within the cache directory - that's where all the html files
> reside. Be sure not to delete .htaccess accidentally :-)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#49 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA1buUHqGYI_NofSFXU6NI7gE5DmEZ74ks5tjA9cgaJpZM4PRqYe>
> .
>
Even with ?action=purge I am seeing some issues with the loading of javascript assets from CDNs over http.
Maybe these could be always loaded via https?
'https://en.cppreference.com/w/cpp/container/vector' was loaded over HTTPS, but requested an insecure script 'http://cdn.jsdelivr.net/ace/1.2.4/noconflict/ace.js'. This request has been blocked; the content must be served over HTTPS.
@natekohl It seems there are other caches where various bits of information are cached. Maybe running purgeList.php --all --purge maintenance script would help?
Yeah, this does kinda feel like two caches are fighting with eachother.
Using ?action=purge on a page works for a minute or two, but then
*something* happens and the old broken behavior returns.
Maybe switching over $wgServer to https has helped with the competing cache
problem -- let's see if it sticks.
In the meantime, it looks like the syntax-highlighted links generated by
GeSHi are hardcoded to http, so pages like
https://en.cppreference.com/w/cpp/utility/tuple/make_tuple will have a mix
of https and http links.
On Fri, Apr 27, 2018 at 9:29 AM Nate Kohl ***@***.***> wrote:
Yeah, this does kinda feel like two caches are fighting with eachother.
Using ?action=purge on a page works for a minute or two, but then
*something* happens and the old broken behavior returns.
On Wed, Apr 25, 2018 at 9:41 PM timsong-cpp ***@***.***>
wrote:
> It looks like a competing cache issue. Have we tried setting $wgServer
> <https://www.mediawiki.org/wiki/Manual:$wgServer> to a protocol-relative
> URL?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#49 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA1bufjtXFzSrt8anrxOgTVDxFGEvG1wks5tsSXdgaJpZM4PRqYe>
> .
>
I meant a protocol-relative URL like //en.cppreference.com etc. (which will follow whatever protocol you are currently using), not just making it https.
The GeSHi thing is probably hardcoded somewhere and should be switched over.
Activity
p12tic commentedon Sep 9, 2017
Could you ask this question on http://en.cppreference.com/w/Talk:Main_Page? The hosting of the website is handled by Nate Kohl, I don't think he monitors this repository.
SylvainCorlay commentedon Sep 9, 2017
Thanks! Closing this issue.
SylvainCorlay commentedon Sep 9, 2017
It does not seem that I have permission to contribute to this page on the wiki.
cc @natekohl
p12tic commentedon Sep 10, 2017
I've unprotected the page temporarily, you can edit now. Sorry for not checking earlier.
SylvainCorlay commentedon Sep 10, 2017
Thanks. I could edit the comments page! 👍
sigurdurb commentedon Mar 23, 2018
@SylvainCorlay Seems like nothing has been done about serving cppreference over https huh? Did you find any other fix ? I am running jupyterhub over https for my uni.
SylvainCorlay commentedon Mar 27, 2018
Hey @sigurdurb sorry for the late reply.
There has been some discussion with @natekohl and @yuvipanda about how to fix this and configure the old version of mediawiki used by cppreference, but no solution to the issue yet unfortunately.
Regarding your use at your Uni, are you using xeus-cling for C++?
p12tic commentedon Mar 27, 2018
Would upgrading MediaWiki to newer version make https support easier? Upgrading will need code changes to the skins though, I have most of that done some time ago, but it's not tested properly yet.
sigurdurb commentedon Mar 27, 2018
@SylvainCorlay Yes, I have it with xeus-cling. Right now I am just testing it but maybe next fall we will start using it with Jupyterhub.
SylvainCorlay commentedon Mar 27, 2018
Awesome! If you have any question on xeus-cling, don't hesitate to hop on our permanent chat. https://gitter.im/QuantStack/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge
natekohl commentedon Mar 27, 2018
p12tic commentedon Mar 27, 2018
The changes are in the upgrade-1.27 branch. They have been done long ago, I don't remember the state of that code.
I'm currently mentoring a programmer that could look into this in several weeks.
natekohl commentedon Mar 27, 2018
povilas commentedon Mar 28, 2018
huh? :)
3 remaining items
SylvainCorlay commentedon Mar 28, 2018
woot!
SylvainCorlay commentedon Mar 28, 2018
This seems to work, but we still need to do
?action=purgeon each new page (I just did it on the front page).Can it be done globally?
natekohl commentedon Mar 28, 2018
natekohl commentedon Mar 28, 2018
p12tic commentedon Mar 28, 2018
@natekohl I think you can just delete the
en,de, etc. directories within the cache directory - that's where all the html files reside. Be sure not to delete .htaccess accidentally :-)natekohl commentedon Mar 28, 2018
natekohl commentedon Mar 28, 2018
natekohl commentedon Mar 29, 2018
SylvainCorlay commentedon Mar 29, 2018
Even with
?action=purgeI am seeing some issues with the loading of javascript assets from CDNs over http.Maybe these could be always loaded via https?
p12tic commentedon Mar 30, 2018
@natekohl It seems there are other caches where various bits of information are cached. Maybe running
purgeList.php --all --purgemaintenance script would help?p12tic commentedon Mar 30, 2018
@SylvainCorlay: The http://cdn.jsdelivr.net/ace/1.2.4/noconflict/ace.js script issue is caused by https://github.com/p12tic/cppreference-doc/blob/master/gadgets/coliru_compiler.js#L548. I've fixed this few seconds ago on the wiki. Unfortunately it seems that http://coliru.stacked-crooked.com/ does not yet support https and we will need some kind of workaround for the "Run this code" button to work.
timsong-cpp commentedon Apr 26, 2018
It looks like a competing cache issue. Have we tried setting
$wgServerto a protocol-relative URL?natekohl commentedon Apr 27, 2018
natekohl commentedon Apr 27, 2018
timsong-cpp commentedon Apr 27, 2018
I meant a protocol-relative URL like
//en.cppreference.cometc. (which will follow whatever protocol you are currently using), not just making it https.The GeSHi thing is probably hardcoded somewhere and should be switched over.