HTTP/3 and php POST

Ryan Gould ryanbgould at
Thu Nov 12 15:51:20 UTC 2020

Thanks for reporting this. 

We have committed a change that can potentially fix this issue: 

Could you please update the source code and report if the issue is indeed fixed for you? 

thank you for solving the problem!  i can confirm that PayPal doesnt
seem to have a problem anymore and that Postman 7.34.0 also seems
happy now.

it might be completely un-related to this problem, but i have noticed
that now a large number php pages are having some difficulty being
consistently displayed.  if i spam the reload key in the browser,
it feels like every third reload will hang and 200 with no content
returned.  Edge seems to handle it gracefully and moves the connection
back to h2.  Firefox will hang the tab until it times out (very odd),
but then it might work the next tab reload.

hello team,

i have found that (current as of 06 Nov 2020)
is having some trouble properly POSTing back to PayPal using php 7.3.24 on
a Debian Buster box. things work as expected using current mainline nginx
or current quiche.  i have verified that PageSpeed is not causing the problem.

the PayPal IPN php script is one of those things that has been working so
long it has cobwebs on it.  it gets a POST, it adds a key / value to the
payload and POSTs it back.  it is instantaneous and thoughtless.  the PHP
script is getting a 200 return code from the return POST and everything
seems great on my side.  but PayPal is complaining about the return POST
and they cant tell me why.  i have enabled logging on the script and in
PHP and dont see anything out of the ordinary.  the only thing i see is
when i use Postman 7.34.0 i am getting a "Parse Error: Invalid character
in chunk size" error, which i am having no luck tracking down information

i would like to generate some --debug logs for you but wont because of the
sensitive PayPal customer payment information.

any thoughts or suggestions?

nginx -V
nginx version: nginx/1.19.4
built by gcc 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)
built with OpenSSL 1.1.1 (compatible; BoringSSL) (running with BoringSSL)
TLS SNI support enabled
configure arguments: --with-cc-opt=-I../boringssl/include --with-ld-opt='-L../boringssl/build/ssl -L../boringssl/build/crypto' --with-http_v3_module --with-http_quic_module --with-stream_quic_module --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/ --lock-path=/var/lock/nginx.lock --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --user=www-data --group=www-data --without-http_uwsgi_module --without-http_scgi_module --without-http_memcached_module --without-mail_pop3_module --without-mail_imap_module --without-mail_smtp_module --with-http_ssl_module --with-http_v2_module --with-http_stub_status_module --with-http_gzip_static_module --with-http_realip_module --with-file-aio --add-module=../../headers-more-nginx-module --add-module=../../pagespeed --http-client-body-temp-path=/var/cache/nginx/client_temp --http-proxy-temp-path=/var/cache/nginx/proxy_temp --http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp --http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp --http-scgi-temp-path=/var/cache/nginx/scgi_temp --with-openssl=../boringssl

as always, thank you for being awesome.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx mailing list