Server starts correctly, but errors appear when I try to consult server URL about rymfony

[maitrepylos]

Same problem

sudo rymfony server:start --port 80
INFO - Starting PHP...
INFO - Running native PHP server with PID 10588
[Mon Aug  3 12:11:34 2020] PHP 7.4.7 Development Server (http://127.0.0.1:65535) started
INFO - PHP server is ready
INFO - PHP started with module CLI
INFO - Starting HTTP server...
INFO - Configured document root: /home/gg/Sites/datt/public/
INFO - PHP entrypoint file: /home/gg/Sites/datt/public/index.php
INFO - Server listening to http://127.0.0.1:80
INFO - HTTP/1.1 GET /
[Mon Aug  3 12:12:15 2020] 127.0.0.1:40138 Accepted
[Mon Aug  3 12:12:15 2020] 127.0.0.1:40138 Invalid request (Malformed HTTP request)
[Mon Aug  3 12:12:15 2020] 127.0.0.1:40138 Closing
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Error(Io(Custom { kind: UnexpectedEof, error: "failed to fill whole buffer" }), State { next_error: None, backtrace: InternalBacktrace { backtrace: None } })', src/http/fastcgi_handler.rs:82:78
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

additional information :

rymfony --version
       # rymfony 0.1

php -v
        # PHP 7.4.7 (cli)

composer --version
       # Composer 1.10.1 2020-03-13 20:34:27

cat /etc/os-release 
      NAME="Linux Mint"
     VERSION="20 (Ulyana)"
      ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 20"
VERSION_ID="20"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.ubuntu.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=ulyana
UBUNTU_CODENAME=focal

cargo --version
       #cargo 1.46.0-nightly (fede83ccf 2020-07-02)

[Pierstoval]

Thanks for reporting this issue!

I think it might come from the fact that the fastcgi handling is buffered instead of being streamed.

I have to make more research about this, since I'm using the fastcgi_client crate and it doesn't seem to have an option to stream the output.

There are also issues with the same crate forcing me to parse the entire HTTP response as a string, which isn't viable in long-term, because this might be incompatible with binary responses or other edge cases I don't know yet.

[kevinpapst]

Likely fixed by #20 - as both reports mention the exact same error I had and both started CLI instead of FPM

[Pierstoval]

@dzc34, @maitrepylos , can you retry with the latest builds? It should be fixed 😉

[Pierstoval]

No answer for some time, and latest releases and refactorings may have fixed this. Feel free to reopen if you encounter this issue again 👍