741 reputation
25
bio website bradler.net
location Kiel, Germany
age 44
visits member for 2 years, 4 months
seen Aug 18 at 11:39

Jun
9
answered Varnish + Nginx + multiple IP addresses
Jun
4
comment Cannot connect to HTTPS port on Ubuntu
Actually it must be something else as I have successfully tested above example. Could you please check your log files. Maybe the responsible issue will be mentioned there.
Jun
4
comment Cannot connect to HTTPS port on Ubuntu
@xofer: Interesting, but it seems that the keyword "ssl" was missing for port 443 directives. So maybe the port was working fine but with HTTP and not (as expected by browsers) with HTTPS.
Jun
4
revised Cannot connect to HTTPS port on Ubuntu
Add missing keyword "ssl" to listen directive. Add all-in-one example
Jun
4
answered Cannot connect to HTTPS port on Ubuntu
May
31
comment Varnish as a web server
@BMDan: Thank you for this important hint. I have updated the pasted code to set proper HTTP status messages.
May
31
revised Varnish as a web server
Update of example codes, based on hints by BMDan regarding obj.response
May
30
comment NGINX downloads text file instead of displaying it
Hmm, *.txt files are included in your mime type definition. So if your text files have the suffix ".txt" Nginx should send the content-type "text/plain". Do you work with the suffix ".txt"?
May
29
comment NGINX downloads text file instead of displaying it
I'm missing your mime-type configuration (can see the file but please post it's content). This is quite helpful to add the correct Content-Type header for different types of provided resources. If your server doesn't send the correct Content-Type your browser acts weird.
May
29
answered Varnish as a web server
May
25
comment Make nginx to pass hostname of the upstream when reverseproxying
@pavel: got it. Actually I did also some research and some tests. It seems that there is no straight approach to fulfill your requirement. So even a "bastardized" solution is a solution. I don't like to ask why you'd like to do this. I'm pretty sure you have your reasons. :-)
May
25
comment Make nginx to pass hostname of the upstream when reverseproxying
@sivann: you are right. has been updated already.
May
25
revised Make nginx to pass hostname of the upstream when reverseproxying
fix type in header name
May
25
comment Varnish ACLs Behind Load Balancer Based on Client's IP
if (req.http.ClientIP ~ "^10\.10\.1\.1([6-8][0-9]|90)$") { ... }
May
25
revised Varnish ACLs Behind Load Balancer Based on Client's IP
fix typo
May
24
answered Varnish ACLs Behind Load Balancer Based on Client's IP
May
24
answered Make nginx to pass hostname of the upstream when reverseproxying
Apr
7
comment CNAME to Amazon does not resolve
I believe it should be "ec2-54-208-90-77.compute-1.amazonaws.com" instead of "ec2-54.208.90.77.compute-1.amazonaws.com".
Apr
2
answered Some users receive untrusted SSL certificate warnings
Mar
29
awarded  Yearling