Tag Info

Hot answers tagged

4

You are probably not using a UTF-8 locale on your system. You can temporarily work around this in your shell by setting your locale to a UTF-8 locale, for instance: export LC_ALL=ur_PK.UTF-8 export LANG=ur_PK.UTF-8


2

Your problem is probably with the sysctl on the Apache servers. Some assumptions: Typically Varnish is vastly faster at processing each connection than a webserver (unless perhaps your Varnish servers have much less CPU, and your Apache servers are only serving static files cached in memory.) I'm going to assume your connections process faster in Varnish ...


2

Varnish cannot connect to FastCGI backend directly. You nee to use your existing webserver for HTTP - FastCGI translation. So, you need to change your existing webserver to another port, and then use that as the backend in Varnish.


1

You should be fine -- I'm guessing you're testing the redirect from the machine running Varnish. On my server running Apache, I can redirect 8080 calls to port 80 (reverse of what you're trying). On server 10.3.1.10: To test my apache exists on port 80 I use netcat to get the web page: root@hp:/etc/apt# nc 10.3.1.10 80 get <!DOCTYPE HTML PUBLIC ...


1

The issue is there : server_name www.example.com example.com ... location / { rewrite ^ https://$server_name$request_uri permanent; } You are responding to domain www.example.com and example.com requests on port 8080 and redirecting to www.example.com because server_name will always match the first server_name value while you are willing to ...


1

Add the cookie to the hash, so everyone with those cookies receives their own version of the cached site content. Documentation here: https://www.varnish-cache.org/docs/trunk/users-guide/vcl-hashing.html Override the default VCL, so having that cookie doesn't automatically mean you don't get cached.



Only top voted, non community-wiki answers of a minimum length are eligible