Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

saveScan malfunctioning #66

Closed
lgalke opened this issue Oct 16, 2017 · 3 comments
Closed

saveScan malfunctioning #66

lgalke opened this issue Oct 16, 2017 · 3 comments
Labels
back-end This issue needs to be addressed by the back-end. bug The issue reports a bug. urgent This issue has top priority.
Milestone

Comments

@lgalke
Copy link
Member

lgalke commented Oct 16, 2017

Response when executing /saveScan ... in Swagger

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Proxy Error</title>
</head><body>
<h1>Proxy Error</h1>
<p>The proxy server received an invalid

response from an upstream server.<br />

The proxy server could not handle the request <em><a href="/locdb-dev/saveScan">POST&nbsp;/locdb-dev/saveScan</a></em>.<p>
Reason: <strong>Error reading from remote server</strong></p></p>
<hr>
<address>Apache/2.4.25 (Debian) Server at locdb.bib.uni-mannheim.de Port 443</address>
</body></html>

On local development setup, there is a cross-origin error:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://locdb.bib.uni-mannheim.de/locdb-dev/saveScan. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
@lgalke lgalke added back-end This issue needs to be addressed by the back-end. bug The issue reports a bug. labels Oct 16, 2017
@lgalke lgalke added this to the Workshop milestone Oct 16, 2017
@lgalke lgalke added the urgent This issue has top priority. label Oct 16, 2017
@lgalke lgalke changed the title saveScan malfunction saveScan malfunctioning Oct 16, 2017
@anlausch
Copy link
Member

Both locally and in the deployment setting the tests are still green. Further investigation showed that there were two problems related to this issue:

  1. server crashes when invalid form-data parameters supplied; Fixed with locdb/loc-db@6e7d59b
  2. server crashes on multipart/form-data when headers are set erroneously due to a middleware problem. Apparently some dependencies changes; Swagger-UI is also related to this issue

Problem 2) needs further investigation and maybe a temporary workaround but the front-end should now not encounter problems anymore if the requests are sent correctly.

@anlausch
Copy link
Member

Back-end problem 2) solved with locdb/loc-db@4286c4d

@lgalke
Copy link
Member Author

lgalke commented Oct 17, 2017

Great, we should keep in mind that the PPN needs to exists in SWB.

@lgalke lgalke closed this as completed Oct 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back-end This issue needs to be addressed by the back-end. bug The issue reports a bug. urgent This issue has top priority.
Projects
None yet
Development

No branches or pull requests

2 participants