Problem/Motivation

Consistently get "HTTP error: 500 when trying to contact crossref.org for XML input" when attempting to use DOI to populate entry. I have confirmed that I have a good account set up with crossref.org

Proposed resolution

Would suggest at least providing a better explanation as to what this error means. I'm not really able to respond to the remainder of this as I have never not gotten this error when attempting this.

Remaining tasks

(reviews needed, tests to be written or run, documentation to be written, etc.)

User interface changes

(new or changed features/functionality in the user interface, modules added or removed, changes to URL paths, changes to user interface text)

API changes

(API changes/additions that would affect module, install profile, and theme developers, including examples of before/after code if appropriate)

Original report by [username]

// Text of original report here.
(for legacy issues whose initial post was not the issue summary)

Comments

rjerome’s picture

rjerome CreditAttribution: rjerome commented

A HTTP 500 error indicates a (fairly) major failure on the server (crossref.org) side.

Fixing 500 errors - general

This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of the Web server site to locate and analyse the logs which should give further information about the error.

St_B’s picture

St_B CreditAttribution: St_B commented
Issue summary: View changes

Hi Ron,
I've got a HTTP error: 400 when trying to contact crossref.org for XML input
On 4 different biblio sites :-/
Must it be also fixed on the web server and not in Biblio ?

St_B’s picture

St_B CreditAttribution: St_B commented

ok guess it must be this https://drupal.org/node/2168853
Have to do some updates...

Alan D.’s picture

Alan D. CreditAttribution: Alan D. commented
Related issues: +#2168853: HTTP error: 400 when trying to contact crossref.org for XML input
Alan D.’s picture

Alan D. CreditAttribution: Alan D. commented
Status: Active » Closed (outdated)

Added the error message to the output, (if given), which is about as far as the module can take things... #2542432: CrossRef data should be sanitized

This should help track actual specifics down if users are still getting issues. We got HTTP 400 twice when rate limited, HTTP 500 once, out of maybe 1000 lookups within 10 minutes (batch update script).