Search results

You'd want something like this to parse .js and .html as PHP (Though seriously, I REALLY don't suggest parsing .js as PHP...) IfModule lsapi_module> AddType application/x-httpd-lsphp .html .htm </IfModule>

You could use mod_rewrite to rewrite .html links to matching .php files.

Hi akinet, I'm not sure where it came from. I'm looking into it now.

Why are you not just using .php? This is the cleanest way to resolve the issue. There is a separate addhandler rule for the new version of Apache.

You had a .htaccess file in the root of your account which contained malformatted code. I've removed it. .htaccess files are not cached by Varnish, nor do you need to use that directive to block access-they're blocked by defautl.

You had a .htaccess file in the root of your account, for some odd reason, that was malformatted. I've removed the file.

Hi, What kind of errors are you experiencing?

Hi mphtechc, What issues are you experiencing, exactly?

Our free hosting comes with community support, as it always has. Unfortunately members of the community aren't able to implement the fixes that need to be implemented. As I've explained to you above, we do not put anything into place without thorough testing, however, obviously some things...

Hi, Our premium servers have been running on Varnish for over two months now with no issues. The issue is not related to Varnish, however it is exacerbated by Varnish's Timeout settings with regard to Litespeed, an Apache Drop-in Replacement that is in use on our free servers. A similar...

bdistler: whats your cPanel username?

We're working on the resolution. We cannot just go and make changes randomly hoping to resolve issues--they have to be tested and re-tested. A fix should be along soon.

This isn't actually an issue with Varnish. It's with the webserver. We're implementing a change that should resolve this.

Hi, This is resolved.

Hi, This has been resolved.

Hi, This should be resolved.

Moved to feedback and suggestions Short answer: When we customize the theme.

This has been resolved.