Comment 3 for bug 1552409

Thomas,
That was one of the things we addressed with EBSCO in this case. It turns out if it's https -> https, it works as per the RFC. Chrome keeps the referring url headers during a 301 but FF does not. Therefore, we used JS to load the final URL from the opac, which works in FF and Chrome. The headers are intact and it's working! The electronic resources are accessible!