Created question in FIWARE Q/A platform on 05-11-2015 at 17:11
Please, ANSWER this question AT https://stackoverflow.com/questions/33550344/502-bad-gateway-and-504-gateway-timeout-in-wirecloud

Question:
502 (BAD GATEWAY) and 504 (GATEWAY TIMEOUT) in Wirecloud

Description:
Time ago we set up a PEP proxy to secure the API our widgets are using. All have being working correctly until today, that we are receiving a 502 Bad Gateway error code for every call going through the proxy.

We have checked the requests are reaching our server and it is responsing correctly to them. The parameters added by the proxy (x-nick-name, x-display-name...) are defined correctly too.

We have also checked the requests outside wirecloud and all go well: we get the token properly and use it in the subsequent calls without problem.

We do not know where this error comes from, any ideas?

EDIT 06/11/2015

After Alvaro's new setting we are receiving the following error in the response body:

{
"description": "Connection Error",
"details": "('Connection aborted.', error(104, 'Connection reset by peer'))"
}

EDIT 09/11/15

Today, the code received in the request's response is different: 504 GATEWAY TIMEOUT

{
"description": "Connection Error",
"details": "('Connection aborted.', error(104, 'Connection reset by peer'))"
}

EDIT 16/11/15

Answering to Mr. Alonso's question:

1.- If we request directly to the server, the response is correctly displayed in the application.

2.- Here you can see the logs from the PEP Proxy with the new line added. As you can see the request is redirected correctly but the info is not displayed in the app.