So, we took a step back in our project and deployed an Hello World
application to see if the problem would still happen.
We used the hello-world example in the Google App Engine code examples and
edited it (our file is attached): there are no differences,
but the fact that we don't have a *.end()* call after we send the response
to the client *res.status(200).send(): *we edited the code
removing the .end() because that is how we do in our project.
We don't think this is the problem. as explained here
<https://stackoverflow.com/questions/20355136/must-res-end-be-called-in-express-with-node-js>
and
seeing that the Express code for *res.send()* does in fact call a
*res.end()* itself.
Anyway, after the hello-world deployment, we still got a 502 Bad Gateway.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/d29945d8-dd6a-490d-9a90-c0f2919c6fbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
'use strict';
const express = require('express');
const app = express();
app.get('/_ah/health', function (req, res) {
res.sendStatus(200);
});
app.post('/data1.aspx', (req, res) => {
res.status(200).send();
});
const PORT = process.env.PORT || 8080;
app.listen(PORT, () => {
console.log(`App listening on port ${PORT}`);
console.log('Press Ctrl+C to quit.');
});
