Last modified: 2014-06-25 19:07:03 UTC
The new Special Page for jobs doesn't follow redirects. [runJobs] Running 1 job(s) via '/w/index.php?title=Special%3ARunJobs <snip> [runJobs] Failed to start cron API: received 'HTTP/1.1 302 Found I can get around it my mucking about with redirect rules, but I'd rather not do that.
In my 1.23.0 installation it doesn't return a 302, and my wiki has $wgLanguageCode = "es", so normally request to Special: go to Especial:, but it doesn't redirect for me when called internally. excerpt of my apache error_log: 127.0.0.1 - - [12/Jun/2014:16:07:33 +0200] "POST /index.php?title=Special%3ARunJobs&tasks=jobs&maxjobs=1&sigexpiry=1402582058&signature=fbc222296801ed1d296b6656fd5c6c9d8d6bfcd4 HTTP/1.1" 202 - "-" "-" Do you have rewrite rules or something like this configured on the server? Did you manage to get where it redirects to?
I managed to put in a RewriteCond that catches the first entry, but it still tosses out the same error at the end because it got a 302 somewhere.
You should: * See the access_log of apache (or the webserver you use) and look for those redirects * Set an appropriate RewriteLog and RewriteLogLevel directives to debug your rewrite rules. You can also access that URL directly from CURL on the same server to debug where it's going to redirect you.
