One could run their staff and OPAC clients on different ports. I'm not saying every combination is sane, but every combination is not accounted for with that code. This code does not account for the sane combination of https (staff) and http (OPAC), nor the strange combination of http (staff) and https (OPAC). I think that she wants to concentrate first on fixing the opac side of this
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5010 --- Comment #62 from M. de Rooy <m.de.rooy@rijksmuseum.nl> --- (In reply to M. Tompsett from comment #61) problem: so only opac-sendshelf. In that case the protocol will hopefully be correct in most cases. Sending a wrong shelf list from staff may be a much smaller issue..
The best way, without the OpacProtocol system preference, is a full-out across the board fix the hard coded 'http' 'https' messes, and require the protocol in OPACBaseURL. Agreed. Like "adjust when resolving the various OpacBaseURL bugs"..
-- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.