204 in HTTP or HTTPS about express HOT 4 CLOSED

Hello, I couldn't reproduce your problem.

here is a project I created trying to reproduce this problem. It is a Minimal, Reproducible Example. Based on what you are trying to do. Here is the source code from this project:

app.js

const express = require('express')
const https = require('https')
const fs = require('fs')
const path = require('path')
const app = express();

app.use('/', (req, res) => {
    res.status(204).end();
});

const options = {
    key: fs.readFileSync(path.join(__dirname, './cert/key.pem')),
    cert: fs.readFileSync(path.join(__dirname, './cert/cert.pem'))
}
const port = process.env.PORT || 8080;
const sslServer = https.createServer(options, app);
sslServer.listen(port, () => {
    console.log(`Secure server is listening on port ${port}`)
});
const anotherPort = process.env.ANOTHERPORT || 8081;

app.listen(anotherPort, () => {
    console.log(`Server is listening on port ${anotherPort}`)
});

Making the request in a browser or a request/response tool (like postman, curl or insomnia) I receive the same results.

Here is the output I collected from curl with command curl -I https://localhost:8080/ -k here I use -k argument is for disable certificate validation (as it is a self-signed certificate). It is stated by the documentation:

HTTP/1.1 204 No Content
X-Powered-By: Express
Date: Thu, 08 Aug 2024 13:19:51 GMT
Connection: keep-alive
Keep-Alive: timeout=5

The same output is shown when used the same server (but now without https), curl -I http://localhost:8081:

HTTP/1.1 204 No Content
X-Powered-By: Express
Date: Thu, 08 Aug 2024 13:20:43 GMT
Connection: keep-alive
Keep-Alive: timeout=5

If you have any concerns, please let me know.

The reason to create a project in GitHub is to keep everything needed to run the project self-contained (an express project and the certificates needed to run the https server).

I generated the certificates using this blog post as a resource.

from express.

Hello, I couldn't reproduce your problem.

here is a project I created trying to reproduce this problem. It is a Minimal, Reproducible Example. Based on what you are trying to do. Here is the source code from this project:

app.js

const express = require('express')
const https = require('https')
const fs = require('fs')
const path = require('path')
const app = express();

app.use('/', (req, res) => {
    res.status(204).end();
});

const options = {
    key: fs.readFileSync(path.join(__dirname, './cert/key.pem')),
    cert: fs.readFileSync(path.join(__dirname, './cert/cert.pem'))
}
const port = process.env.PORT || 8080;
const sslServer = https.createServer(options, app);
sslServer.listen(port, () => {
    console.log(`Secure server is listening on port ${port}`)
});
const anotherPort = process.env.ANOTHERPORT || 8081;

app.listen(anotherPort, () => {
    console.log(`Server is listening on port ${anotherPort}`)
});

Making the request in a browser or a request/response tool (like postman, curl or insomnia) I receive the same results.

Here is the output I collected from curl with command curl -I https://localhost:8080/ -k here I use -k argument is for disable certificate validation (as it is a self-signed certificate). It is stated by the documentation:

HTTP/1.1 204 No Content
X-Powered-By: Express
Date: Thu, 08 Aug 2024 13:19:51 GMT
Connection: keep-alive
Keep-Alive: timeout=5

The same output is shown when used the same server (but now without https), curl -I http://localhost:8081:

HTTP/1.1 204 No Content
X-Powered-By: Express
Date: Thu, 08 Aug 2024 13:20:43 GMT
Connection: keep-alive
Keep-Alive: timeout=5

If you have any concerns, please let me know.

The reason to create a project in GitHub is to keep everything needed to run the project self-contained (an express project and the certificates needed to run the https server).

I generated the certificates using this blog post as a resource.

I use http://localhost:8080 and a cloud server in the same environment, my function is. return HttpResponse( json.dumps({'message':'delete successfully '})，content_type='application/json'，status=204) ,when i use curl ,the data will be deleted in database and the program will over, but when i use curl to request the cloud server (https), the data also be deleted, but the program without any response, when I debug in the chrome, i saw the status and size is “(pending)”,

from express.

@oceanusXXD how is your problem related to Express?

This is Python code, not JavaScript:

return HttpResponse(json.dumps({'message':'delete successfully '})，content_type='application/json'，status=204)

from express.

@oceanusXXD how is your problem related to Express?

This is Python code, not JavaScript:

return HttpResponse(json.dumps({'message':'delete successfully '})，content_type='application/json'，status=204)

Sorry~I will close it soon, but if you can reproduce this issue on your local or cloud server, it may indicate that it is a common problem.

from express.