New answers tagged http
Just a quick note that a 500 internal server error is an issue with your actual server. If you want to test this in the future, then you can run this command in terminal to see what your server is returning: curl -v -H 'Host: yourdomain.com' yourserver IP (replace with your actual domain & your server IP address in those fields).
A URL is an address used to locate documents. Examples of URLs are: http://example.com/mypage.html ftp://example.com/download.zip mailto:firstname.lastname@example.org file:///home/user/file.txt tel:1-888-555-5555 http://example.com/resource?foo=bar#fragment HTTP is the protocol used to fetch some URLs (the ones that start with http://) from servers. A simple HTTP ...
When new content is launched, it may not be absolutely critical that users see it right away. In that case you could relax your cache controls and allow your content to be cached for an hour or two and not require that the user re-validates. Actually with "must-revalidate", I don't see any point in not allowing your pages to be cached forever. Otherwise ...
Strangely enough, I got it to work by deleting some already-deactivated plugins. Someone suggested I'd deactivate plugins, so there's where I headed and it worked well. One was WP Super Cache, because I switched to W3 Cache. Another was XML Sitemap plugin. All works good now, thanks everyone!
If the 500 error is coming from your own site, you should be able to address the problem by looking in the server's error log. 500 errors are produced any time something happens that the web server is not expecting. It is unusual to see a 500 error with the full content of the page, but it is not unheard of. The server log will have the cause of the error ...
Top 50 recent answers are included