Versions Compared

Old Version 36

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 37

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • In Chrome, go to "More Tools → Developer Tools".  Then try to reproduce the error back in your open browser tab. 
    • The "Console" tab will provide a brief overview of errors that have occurred in this tab of your browser.
    • The "Network" tab will provide more information on where the error appeared (as the request that threw an error will appear in red).  Clicking the red request will show you the exact Headers sent/returned and the error Response.
  • In Firefox, go to "Web Developer → Web Developer Tools". Then try to reproduce the error back in your open browser tab. 
    • The "Console" tab will provide a brief overview of errors that have occurred in this tab of your browser.
    • The "Network" tab will provide more information on where the error appeared (as the request that threw an error will appear in red/purple).  Clicking that request will show you the exact Headers sent/returned and the error Response.
  • In Microsoft Edge, go to "More Tools → Developer Tools".  Then try to reproduce the error back in your open browser tab.
    • The "Console" tab will provide a brief overview of errors that have occurred in this tab of your browser.
    • The "Network" tab will provide more information on where the error appeared (as the request that threw an error will appear in red).  Clicking the red request will show you the exact Headers sent/returned and the error Response.
Note

If the User Interface error is a generic 500 response, that means there's an error that occurred on your backend.  Check your DSpace logs or Tomcat logs for information on the exact error.  See the below section on "Finding error messages in the REST API logs".

Finding error messages in the REST API logs

...