[🐛 BUG]: Static middleware causes ERR_CONTENT_LENGTH_MISMATCH

[tux-rampage]

No duplicates 🥲.

• I have searched for a similar issue in our bug tracker and didn't find any solutions.

What happened?

I configured an application as follows:

version: "2.7"

server:
  command: "php /app/backend/roadrunner.php"

logs:
  mode: development
  encoding: console
  level: info

rpc:
  listen: tcp://127.0.0.1:6001

http:
  address: 0.0.0.0:3000
  access_logs: true
  raw_body: false
  pool:
    debug: true

  middleware:
    - static
    - sendfile
    - headers

  uploads:
    dir: /var/uploads
    forbid:
      - ".php"
      - ".exe"
      - ".bat"
      - ".sh"
  headers:
    response:
      X-Powered-By: "roadrunner/php"

  static:
    dir: /app/public/dist/de
    calculate_etag: false
    response:
      X-RoadRunner-Source: Static

For some resources that will be served by the static middleware (identified by the header X-RoadRunner-Source from the config above), the browser rejects the resource with ERR_CONTENT_LENGTH_MISMATCH (webkit) or NS_ERROR_NET_PARTIAL_TRANSFER (firefox).

This does not happen for all files, some are served without any problems, while others are broken. The only difference that i can currently spot is the file size. It seems to happen when a file exceeds 16k. Could this be a buffer problem?

Version (rr --version)

• rr version 2023.1.4 (build time: 2023-05-25T11:10:19+0000, go1.20.4), OS: linux, arch: amd64
• rr version 2.12.2 (build time: 2023-01-12T12:07:45+0000, go1.19.5), OS: linux, arch: amd64

How to reproduce the issue?

See yaml in the description

Relevant log output

No response

[rustatian]

Hey @tux-rampage 👋🏻
Interesting, I think that this is the ServeContent limitation but I'll dig into that. Thanks for the report 👍🏻

[rustatian]

BTW, could you try to remove the Accept-Ranges: bytes header, since this middleware doesn't support that header?

[tux-rampage]

BTW, could you try to remove the Accept-Ranges: bytes header, since this middleware doesn't support that header?

How should I do that? I did not configure that and RR seems to send it from the Middleware (Those are the response headers).

[rustatian]

Oh, yeah. Could you try then to use just plain curl request, w/o browser? I think, when I saw this header, that RR tries to respond with some of the Ranges headers.

[tux-rampage]

Sure. In the meantime for completeness, here are the Request headers. I just needed to strip some private information:

[tux-rampage]

All right, same issue with a CURL request:

> curl --verbose -s http://localhost/styles.css -o /dev/null; echo "Exit Code: $?"
*   Trying 127.0.0.1:80...
* Connected to localhost (127.0.0.1) port 80 (#0)
> GET /styles.css HTTP/1.1
> Host: localhost
> User-Agent: curl/7.81.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Accept-Ranges: bytes
< Content-Length: 82399
< Content-Type: text/css; charset=utf-8
< Last-Modified: Tue, 06 Jun 2023 08:09:44 GMT
< X-Powered-By: roadrunner/php
< X-Roadrunner-Source: Static
< Date: Tue, 06 Jun 2023 10:09:43 GMT
< 
{ [16863 bytes data]
* transfer closed with 65536 bytes remaining to read
* Closing connection 0
Exit Code: 18

[rustatian]

Ok, thanks for this investigation 👍🏻 I'll write a tests with a big static file to confirm this and then dig into the problem. I thinks this is a http server limitation and I would be able to raise the limits. Expected fix should be this Thursday in v2023.1.5.

[tux-rampage]

Awesome. Thanks for the quick reaction 👍

[rustatian]

Funny thing here, if you copy the file curl ... -o some_file (instead of /dev/null) it would be of the correct size and correct content.

[rustatian]

@tux-rampage Are you using nginx or some web-server in front of the RR ?

[rustatian]

@tux-rampage Found the bug. Could you please remove the send middleware and retry the request?

[tux-rampage]

Hi @rustatian

Thanks for the quick solution. I have retested it with v2023.1.5 and can confirm that this issue is solved. 👍🏻

[rustatian]

Hey @tux-rampage 👋🏻 Cool, nice to hear that ⚡