Entering a PID that is recognized as belonging to a CMDI-providing repo but which returns something else (eg HTML), example http://hdl.handle.net/11858/00-246C-0000-0023-8C44-B, currently leads to a generic HTTP/500 error page.
Would be helpful to present something more detailed. Worst case opt-out the DOG from the generic proxy error messages.
Entering a PID that is recognized as belonging to a CMDI-providing repo but which returns something else (eg HTML), example http://hdl.handle.net/11858/00-246C-0000-0023-8C44-B, currently leads to a generic HTTP/500 error page.
Would be helpful to present something more detailed. Worst case opt-out the DOG from the generic proxy error messages.