You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following message from John Kunze affects this codebase as there are hard-coded references to http://n2t.net/ezid.... Just an FYI :)
John Deck
Message from John Kunze:
As previously announced, EZID's URL was switched from http://n2t.net/ezid
to http://ezid.cdlib.org last night. If you have not already done so,
please update your bookmarks and API clients. As before, this means that
The persistent links, expressed as URLs, of the ARKs and DOIs
that EZID creates will not change.
While browsers will be redirected from the old URL to the new URL for at
least 1 year, the situation is different for API clients.
For API clients, direct PUT and POST requests against the old URL will be
supported for 1 month. If your API client is experiencing difficulty in
establishing a secure connection to the old URL, it is likely due to your
client's SSL library not supporting a feature called "TLS server name
indication support (RFC 4366)". The easiest remedy is simply to switch
your client to use the new URL, although it is also possible to configure
your client to be able to connect anyway, such as setting up a local
"trust store".
The text was updated successfully, but these errors were encountered:
Following message from John Kunze affects this codebase as there are hard-coded references to http://n2t.net/ezid.... Just an FYI :)
John Deck
Message from John Kunze:
As previously announced, EZID's URL was switched from http://n2t.net/ezid
to http://ezid.cdlib.org last night. If you have not already done so,
please update your bookmarks and API clients. As before, this means that
http://ezid.cdlib.org .
that EZID creates will not change.
While browsers will be redirected from the old URL to the new URL for at
least 1 year, the situation is different for API clients.
For API clients, direct PUT and POST requests against the old URL will be
supported for 1 month. If your API client is experiencing difficulty in
establishing a secure connection to the old URL, it is likely due to your
client's SSL library not supporting a feature called "TLS server name
indication support (RFC 4366)". The easiest remedy is simply to switch
your client to use the new URL, although it is also possible to configure
your client to be able to connect anyway, such as setting up a local
"trust store".
The text was updated successfully, but these errors were encountered: