Migration and upgrade

Fragment of a discussion from Robowiki talk:About
Jump to navigation Jump to search

Can we not forcefully redirect? I think it breaks my rss reader and probably others too.

If someone wants to use https, I understand them. But one day the certificate will expire, and stupidly paranoid modern browsers do not even let you see pages behind expired certificates.

Out edits are public anyway, I see no harm someone sniffing them.

Yes, I know that sometimes pages content is modified by evil providers but I think it is less harm than not able to see content of a page at all.

Beaming (talk)20:58, 20 April 2020

It fixed a bug with the login, which redirected back to http for some reason. I'll add an exception for the RSS URL to not do redirect, like I did for the roborumble. Can you think of any other URLs which need exceptions?

Skilgannon (talk)21:03, 20 April 2020

Exception added for anything using api.php

Skilgannon (talk)21:51, 20 April 2020

There is some differnces between new and old wikis.

The old one had some special api enabled. Specificly there were working two special urls

http://robowiki.net/w/ http://robowiki.net/api.php

they allowed to check for incremental changes.

They also gave access to rss reader.

Beaming (talk)21:54, 20 April 2020

Ok, I'm not sure how that was set up exactly. It is better not to have php files in the root namespace, or using directory defaults for file access. But there is now: http://robowiki.net/w/api.php

This should have what you need.

Skilgannon (talk)22:05, 20 April 2020

This seems to work. Let's keep it during migration stage. Once users are back and rediscover new mechanism, we can put it back to wiki pristine way of handling apis.

Beaming (talk)22:09, 20 April 2020