• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question AH01070: Error parsing script headers

Giorgio1

New Pleskian
I need some help to debug this situation!

The problem
I get a lot of these error in apache error_log:

Code:
AH01070: Error parsing script headers

Actual settings:

CentoOS 7.4, Plesk Onyx 17.5.3

Hosting settings:
- PHP 7.1.15
- FPM application served by Apache

nginx settings:

"Proxy mode" and "Smart static files processing" enabled.

Additional nginx directives:

Code:
gzip on;
gzip_disable "MSIE [1-6]\\.(?!.*SV1)";
gzip_proxied any;
gzip_comp_level 5;
gzip_types text/plain text/css application/javascript application/x-javascript text/xml application/xml application/xml+rss text/javascript image/x-icon image/bmp image/svg+xml;
gzip_vary on;

I found that when I load a page of this Wordpress website with Chrome DevTools > Network -> Disable cache, there are no error. If I uncheck "Disable cache" and I reload the page, apache writes the error in error_log.

In the Wordpress website there is WP Super Cache.

What could be the problem? Thanks for any suggestion.
 
Some more details. In WP Super Cache was active the setting "304 Not Modified browser caching. Indicate when a page has not been modified since it was last requested. (Recommended)".

When I disabled this setting, the status of the page is 200 and it seems that there isn't anymore the error in error_log.

Any comments are welcome...
 
I read about that but I was not sure it's related. I have also a couple of 503 error in Google Search Console, so I will continue to investigate...
 
Back
Top