Ultimate don't set correct content-type in some case #193

cesco69 · 2025-05-09T13:03:25Z

Hi, in some case ultimate-express return text/html for application/octet-stream (like express). See this snippet

// must support body reading with different limits

const express = require("ultimate-express");

const app = express();

app.use(express.json({ limit: '100kb' }));
app.use(express.raw({ limit: '50mb' }));
app.use(express.urlencoded({ limit: '50mb' }));

app.post('/abc',  (req, res) => {
    res.send(req.body);
});

app.listen(13333, async () => {
    console.log('Server is running on port 13333');

    const ab = new ArrayBuffer(1024 * 1024 * 10);
    const u8 = new Uint8Array(ab);

    for(let i = 0; i < u8.length; i++) {
        u8[i] = i % 256;
    }

    const response = await fetch('http://localhost:13333/abc', {
        method: 'POST',
        body: ab,
        headers: {
            'Content-Type': 'application/octet-stream'
        }
    });

    const text = await response.arrayBuffer();
    console.log(response.headers.get('content-type')); // Add this check! <----------------------------------------------
    console.log(text);

    process.exit(0);

});

output

  +   'text/html; charset=utf-8\n' +
  -   'application/octet-stream\n' +

The text was updated successfully, but these errors were encountered:

This was referenced May 9, 2025

feat: test middleware [POC: DON'T MERGE] #192

Closed

fix: default content type #200

Merged

dimdenGD closed this as completed in #200 May 10, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Ultimate don't set correct content-type in some case #193

Ultimate don't set correct content-type in some case #193

Uh oh!

Ultimate don't set correct content-type in some case #193

Ultimate don't set correct content-type in some case #193

Comments

Uh oh!