What's the net::ERR_HTTP2_PROTOCOL_ERROR about?

✔ Recommended Answer

I didn't figure out what exactly was happening, but I found a solution.

The CDN feature of OVH was the culprit. I had it installed on my host service but disabled for my domain because I didn't need it.

Somehow, when I enable it, everything works.

I think it forces Apache to use the HTTP2 protocol, but what I don't understand is that there indeed was an HTTP2 mention in each of my headers, which I presume means the server was answering using the right protocol.

So the solution for my very particular case was to enable the CDN option on all concerned domains.

If anyone understands better what could have happened here, feel free to share explanations.

Source: stackoverflow.com

Answered By: Tristan G

Method #2

The net::ERR_HTTP2_PROTOCOL_ERROR is an error message that appears in a web browser when there is an issue with the HTTP/2 protocol while communicating with a server.

HTTP/2 is a relatively new protocol that was designed to improve the performance of websites, particularly for users with slow or unreliable connections. However, since it is a relatively new technology, some servers and browsers may not fully support it, which can result in errors like net::ERR_HTTP2_PROTOCOL_ERROR.

This error can occur due to several reasons, including:

  1. Incompatibility: The server and browser may not be fully compatible with HTTP/2, leading to issues in communication.

  2. Network issues: The connection between the server and browser may be unstable or unreliable, resulting in the protocol error.

  3. Server configuration issues: The server may be misconfigured, resulting in protocol errors.

  4. Browser issues: The browser may have issues with the way it handles the HTTP/2 protocol, leading to the error.

If you encounter this error, you can try reloading the page, clearing your browser cache, and updating your browser to the latest version. If the problem persists, you may need to contact the website's technical support team for further assistance.

Comments

Post a Comment

Most Popular

PhpStorm, return value is expected to be 'A', 'object' returned

Image
✔ Recommended Answer Has to be because object can be ANY class instance, even B etc. You can annotate the create() method with generics PHPDoc to tell that the return type will be the same as the input parameter class string. It gives more context info to the IDE. /** * @template T * * @param string $class * @return T */ private function create(string $class) : object { return new $class(); } P.S. Instead of create('B'); better use create(B::class) . This way the IDE can track the usages of that class for refactoring/search purposes etc. Source: stackoverflow.com Answered By: LazyOne Method #2 This error message suggests that your code is expecting a value of type 'A' to be returned, but instead, the code is returning an object. This error can occur in PhpStorm, or any other PHP development environment. To resolve this error, you should check the function or method that is returning the object and ensure that it is returning
Read more

Remove Unicode Zero Width Space PHP

✔ Recommended Answer This: $newBody = str_replace("​", "", $newBody); presumes the text is HTML entity encoded. This: $newBody = str_replace("\xE2\x80\x8C", "", $newBody); should work if the offending characters are not encoded, but matches the wrong character (0xe2808c). To match the same character as #8203; you need 0xe2808b: $newBody = str_replace("\xE2\x80\x8B", "", $newBody); Source: stackoverflow.com Answered By: Jef Method #2 To remove Unicode zero width space (ZWSP) from a string in PHP, you can use the str_replace() function to replace the ZWSP character with an empty string. Here's an example: php $str = "Hello​ World" ; // Contains ZWSP after "Hello" // Replace ZWSP with an empty string $str = str_replace ( "\u{200B}" , "" , $str ); echo $str ; // Outputs "Hello World" without ZWSP In this example, the str_replace() functi
Read more

Laravel file upload returns forbidden 403, file permission is 700 not 755

✔ Recommended Answer The issue you are facing could be due to incorrect file permissions for the storage folder. Here are some steps to fix the problem: SSH into your cPanel server. Change the permission of the storage folder to 755: chmod -R 755 storage/ This command will change the permission of the storage folder and all its contents to 755, which should give the web server permission to read and write to the folder. Check the ownership of the storage folder. Ensure that the owner of the folder is the same as the user running the web server (typically www-data on Apache): ls -l This command will list the files and folders in the current directory along with their ownership and permission details. Make sure that the owner of the storage folder is the same as the user running the web server. If the ownership is incorrect, you can change it using the following command: chown -R www-data:www-data storage/ This command will change the ownership of the storage folder and all its conten
Read more