Change port of wordpress
@annie you should change both siteurl and home option_name values to e.g http://localhost/wordpress:9000
@annie you should change both siteurl and home option_name values to e.g http://localhost/wordpress:9000
Headers manipulation should be done before template output starts. In WordPress it is typically done in template_redirect hook, which is right before template load but after core has fully loaded.
Since wordpress’s execution logic relies on parameters filled by the php-apache connector (mod_php) running a php command line is not guarantied to produce the same results or any at all, all depending on your local settings. In any case, you should not check if your server is functioning from the server itself as there other … Read more
From quick look at source mechanics seem very similar, my first suggestion for WP would be to try and bump HTTP transport to curl (I do it with plugin in WP so no idea about specific code). curl seems to be considerably more robust for corner cases and it’s not WP’s first choice.
Ad Timeout You should be able to get around the timeout using a filter add_filter( ‘http_request_timeout’, ‘wpse35826_timeout_extd’ ); function wpse35826_timeout_extd( $time ) { // Default timeout is 5 return 10; } Choose the right protocol/scheme About your protocol/scheme problem: If it’s your local install, you can use the conditional. function wpse35826_remote_get( $args ) { $protocol … Read more
Just try to disable “HTTP/2 push” under the Minify section of W3 Total Cache. Most probably your apache server (or whatever web server you are using) does not support http2. The browser understands that, and it’s trying to tell you that the preload is not worth it. More about the difference between http1.1 and http2, … Read more
For the record, I have uninstalled curl and wordpress was working on seamlessly. So I confirm that curl is not a dependency of wordpress. However, some plugins may require curl.
We tracked it down to content-encoding’ => string ‘deflate’ (length=7) being at fault. WP_HTTP is adding in a deflate header for no reason and un gzip compressing the results. It only happens when the body of the response is under a certain string length. Very annoying when all you want isa 1 or a 0. … Read more
Does WordPress only support HTTP 1.1?
Is this meant to be used on sites in production? Yes. Many sites have been already using it. Is there a security risk to allowing endpoints to be viewed by anyone, such as /wp-json/wp/v2/users/ which shows all users registered to the site? No. Server responses have nothing to do with security, nothing you can do … Read more