[Bug] SetHttpHandler returns invalid responses and missing POST data

[AdrianIsBored]

Summary

SetHttpHandler doesn't work properly, the handler function executes but the responses generated by res.send() are returning invalid HTTP status

POST request data is also not passed to setDataHandler and setCancelHandler is triggered instead

setDataHandler doesn't run at all

Same resource works fine on legacy artifact

Issue type

Server

Repro rate

Always

Server build version

b90

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

Windows

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

Yes

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Create and run a resource with the following server script:

SetHttpHandler(function(req, res)
    print('Http request')
    print("method: ", req.method)
    print("path: ", req.path)

    req.setDataHandler(function(data)
        print(data)
        res.send("ok")
    end)

    req.setCancelHandler(function()
        print("cancel")
    end)
    res.send("boo")
end)

2. Send a POST request with example body of hello curl -X POST http://127.0.0.1:30120/test -d hello

Expected Behavior

setDataHandler should execute and receive the body and print:
hello

and the response should be valid

Actual Behavior

The request handler runs but setDataHandler doesn't run and responses are invalid

Evidence

Legacy artifact output using the same resource:
Http request
method: POST
path: /
hello

POST/GET returns: "ok"/"boo" respectively

Enhanced artifact output:
Http request
method: POST
path: /
cancel

POST/GET returns: invalid http response

Additional Context

No response

[FingerlessGlov3s]

Getting this problem also

[JackCosens]

Yep can confirm we're having the same issue.

[dexslab]

I can confirm this is broken

[wolfram-cfx]

Thanks, we are looking into this.

[dexslab]

Also setting http2 convar doesnt allow it to work as well

[wolfram-cfx]

There is no http2 anymore. It got removed.

[Gogsi]

A fix for this bug has been implemented and is available in August 11 Patch. Please try again and let us know if the issue persists. Thanks for your help!