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
discovered when working with @cbeer that fetching a particular PURL via HTTP doesn't seem to follow redirection on our aliased domains. the output of the following two (example) commands is different:
because purl-stage is an alias for sul-purl-stage, the former command fails somewhat silently — the empty response body of the redirect results in the fetched record having no unique identifier, so it is skipped for indexing. if sul-purl-stage is used instead, the real publicXML can be fetched.
this behavior may be ruby implementation dependent — a first place to look might be:
discovered when working with @cbeer that fetching a particular PURL via HTTP doesn't seem to follow redirection on our aliased domains. the output of the following two (example) commands is different:
because
purl-stage
is an alias forsul-purl-stage
, the former command fails somewhat silently — the empty response body of the redirect results in the fetched record having no unique identifier, so it is skipped for indexing. ifsul-purl-stage
is used instead, the real publicXML can be fetched.this behavior may be ruby implementation dependent — a first place to look might be:
searchworks_traject_indexer/lib/sdr_stuff.rb
Lines 27 to 35 in b2175d2
The text was updated successfully, but these errors were encountered: