OJS 2.4.8, LOCKSS and https

Hi,

we recently changed to https only for all journals (force_ssl = On) on an OJS 2.4.8.3 multi-journal installation.

Unfortunately, LOCKSS (we use public LOCKSS) cannot crawl anymore the newest issues. This is what they report:

PROBLEM URL:
The URL http://www.psychoanalyse-journal.ch/index.php/psychoanalyse/gateway/
lockss?year=0 is being redirected to the unexpected URL https://
www.psychoanalyse-journal.ch/index.php/psychoanalyse/gateway/lockss?year=0?
year=0
If you look closely at the end of the unexpected URL, you’ll see that the
query string “?year=0” at the end of the URL is repeated twice even though the
query string was only listed once in the original URL.

It seems that there may be a problem in the LOCKSS plug-in that handles the request.

config.inc.php:
restful_urls = off (=on makes problems in the breadcrumb, the last entry of the breadcrumb generates a wrong URL including the journal name)

We do have some Rewrite rules in .htaccess, but they should not have not any effect:

Journal für Psychoanalyse

RewriteCond %{SERVER_NAME} ^www.psychoanalyse-journal.ch
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ index.php/psychoanalyse/$1 [L]

General rule for removing index.php

RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ index.php/$1 [QSA,L]

(even if QSA is removed, the year=0 query part is appended twice)

Thanks for any hint how to solve the LOCKSS URL problem

We got the following message from A. Ohlson, LOCKSS:
“I believe the problem to be a bug in the OJS2 software. Perhaps they just did an upgrade that introduced it, but today I discovered the same issue across several other publishers, all on OJS 2.4.8. So the issue probably isn’t something you can resolve yourself but you could raise it with PKP. We will report it as well. In the mean time, we’re working on a fix at our side that will strip off redundant arguments and we will let you know if we release a version of the plugin that will allow preservation of your content even before PKP resolves the problem.”

Issue opened in Github: LOCKSS and https · Issue #4124 · pkp/pkp-lib · GitHub