[Junior Tidal]

We’re encountering a problem here at City Tech. Our EZ Proxy URL changes just on mobile devices from citytech.ezproxy.cuny.edu:2048/login?url= to citytech.ezproxy.cuny.edu/login?qurl=

We’ve reported the problem to Roland, but I was curious if anyone else has come across this?

[Stephen Klein]

I proxy by hostname to avoid having to use prots in my URL string:
https://www.oclc.org/support/services/ezproxy/documentation/cfg/proxybyhostname.en.html

[Alevtina Verbovetskaya (she/her)]

I’m having a lot of difficulty accessing the NYCCT Library website. Is it just me?

[Monica Berger]

Probably not. When I used the Tor emulator to try to troubleshoot all of this earlier, it took forever for each page to load.

[Roland Samieske]

Hello:
I’m trying to confirm if this is a result of using “ForceHTTPSLogin” in the EZproxy config. Only because this URL change seems to have happened right after its implementation.
I could find a reference here:
http://www.oclc.org/support/services/ezproxy/documentation/changes.en.html
“allows starting point URLs to take the form:
http://ezproxy.yourlib.org:2048/login?qurl=http%3a%2f%2fwww.somedb.com
Special characters that appear after qurl= must be “hex quoted,” especially & to %26, = to %3d and ? to %3f. As such, the URL (one or more line breaks were added in each of the following two examples for display purposes; examples without added line breaks are available):
http://ezproxy.yourlib.org:2048/login?url=http://www.somedb.com/search?
name=db&option=1
would need to be changed to:
http://ezproxy.yourlib.org:2048/login?qurl=http%3a%2f%2fwww.somedb.com
%2fsearch%3fname%3ddb%26option%3d1
This alternate form is not required, but is provided for instances where using a character encoded URL is useful.”

For example, if you run the encoded URL (i.e. the URL after the “qurl” parameter) through a decoder ( http://www.asiteaboutnothing.net/c_decode-url.html ), it reverts through the regular, plain URL.

I’m not sure that the encoded URL is the problem here. More likely, the network that the mobile user is connected to may not have the standard SSL port 443 open.

I’m seeing this qurl switch when using a desktop browser as well.

I’ll post whatever I can find out later.

And yes: the NYCCT library site is painfully slow.

[Junior Tidal]

We had a server outage last week due to overheat. I hope its not a hardware problem.

Both our desktop site and mobile site (which is pretty light in terms of file size) seem pretty slow off-campus.

[Author]

Posts