New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
http2 issue with curl #14105
Comments
I think it would be better to find the reason why this error happens instead of forcing http 1.1, because a server might not support it in the future. |
If your server instructs clients to use HTTP2 and then fails to respond to HTTP2 requests then there might also be a fraction of your website visitors for which this HTTP request fails and who therefore will never show up in Matomo. Therefore I'd recommend you to troubleshoot your server first. (or check if you are using an outdated curl version in case this is a curl bug) |
I don't think this seems like an issue in Matomo? Can we close the issue here? And if needed discuss further in the forum maybe or continue discussing here but keep the issue closed unless there is a bug in Matomo? |
Here is my
When I run the curl command from my server I got a normal answer
But from PHP I got an issue. I'll try to reproduce it in a script for my hoster and ask him. What more could I give you to track this issue? You can also close it as it's not really a Matomo issue if you prefer not to handle a protocol switch (which makes sense) |
I'm pretty sure your cURL does not support http2:
To test this, run |
You're right.
But PHP seems to be running a different curl... Might be something like https://framagit.org/hubzilla/core/issues/1291#note_345604 ? |
FYI I'll close this issue for now. Feel free to continue discussing and to reopen if there's an issue with Matomo and not the server itself. |
I have an issue blocking my archiving process:
Lines we're looking at are:
After digging a little without much findings, I got it fixed by adding in
$curl_options
ofHttp.php
So it might be useful to add in settings a flag to choose which HTTP_VERSION should be used by curl for cases like this?
The text was updated successfully, but these errors were encountered: