594 reputation
19
bio website
location
age 18
visits member for 1 year, 11 months
seen Jul 31 at 19:43

Junior IT Security student at Ruhr University Bochum.
Collecting experiences with

  • Web Application Development,
  • Database Administration and
  • Data Modelling.

Also actively working with HTTP, Web Infrastructure, and especially .


Jul
31
comment Proxy to SSL site (on another server) from a non SSL site
I see no reason why it should not work - did you try to use SSLProxyEngine on? The documentation (httpd.apache.org/docs/2.2/mod/mod_ssl.html) lists numerous SSLProxy* directives to configure trusted certificates/CAs and enable certificate verification (no verification per default). SSL/TLS clients don't need an own certificate/private key pair to connect to an SSL/TLS-enabled server (except if the server requires certificate-based client authentication; this is also possible with SSLProxyMachineCertificate* directives).
Jul
31
comment nginx auth_basic 401 htpasswd
I wonder why you added proxy_pass_header Authorization;. Authentication is done in nginx so there is no need to pass the relevant header upstream. Maybe the Authorization header confuses your upstream to return 401? Try removing/commenting out the directive.
May
25
comment Continuous segmentation faults (code 11) with nginx and php-fpm
Static files should be no issue anyway since they should be processed by nginx. Whatever load I had, I have never seen PHP segfaulting because of it (usually PHP-FPM will be really busy and upstream requests coming from nginx will time out). Try disabling modules one after another and see when the segfaults stop. You might want to reinstall all your extensions as well (don't know how that goes on CentOS) and check that their versions match PHP. Did you update anything before the segfaults started?
Apr
12
revised SSL Certificate implementation for a stack that has varnish and multiple NGINX webservers
adding stud
Apr
11
comment SSL Certificate implementation for a stack that has varnish and multiple NGINX webservers
@sridharpandurangiah Wait, wasn't your initial thought to pass SSL through Varnish? I intend to point the A record of the domain to the Varnish server so that I can benefit from Varnish's caching instead of loading the NGINX server. Of course you can configure stunnel to directly forward to nginx but wouldn't that defeat the purpose of the question? If you wanted to not pass through Varnish then your current setup is fine, isn't it?
Apr
11
comment SSL Certificate implementation for a stack that has varnish and multiple NGINX webservers
@sridharpandurangiah Either that, or you let Varnish also listen on port 80 and your SSL terminator on port 443. Other than web servers and proxies/load balancers, stunnel is a plain SSL terminator, meaning it cannot do anything but terminate SSL. Hence, stunnel should only listen on port 443. For web servers and proxies, you may want to use additional features on your front-end like compression (compressing on your backend would make Varnish cache a version for each compression being used -- deflate, gzip and, none). If SSL is your only concern, stunnel would probably be best.
Apr
11
revised SSL Certificate implementation for a stack that has varnish and multiple NGINX webservers
added 177 characters in body
Apr
11
answered SSL Certificate implementation for a stack that has varnish and multiple NGINX webservers
Apr
10
revised Nginx removes Content-Length header for chunked content
Adding X-Accel-Buffering and proxy_buffering
Mar
23
revised How to make an existing caching Nginx proxy use another proxy to bypass a firewall?
minor config fix
Mar
23
answered How to make an existing caching Nginx proxy use another proxy to bypass a firewall?
Sep
30
comment Nginx removes Content-Length header for chunked content
@VBart Sure there are standards - but there's only very few information about how far particularly nginx implements them.The TCP proxy module is hust a suggested workaround.
Sep
27
awarded  Yearling
Aug
23
answered Microcaching with nginx & uwsgi
Aug
22
comment Apache to Nginx rewrite rules
My answer is just an alternative to yours and mainly for the purpose of better understanding the rewrite flags in nginx (break vs. last) because there's often confusion about what they do.
Aug
22
answered multiple cert in a file?
Aug
22
answered Apache to Nginx rewrite rules
Jun
1
awarded  Critic
May
7
comment Cannot hit nginx from outside localhost
warstarz.com still resolves to 69.162.77.100, so that definitely is a problem. I emulated a request like this: curl -v -H "Host: warstarz.com" http://69.162.77.106, but this gets me a response from Apache. Does nginx actually start?
Apr
9
comment Why does nginx not send the Content-Length header when the request is HEAD?
How to you connect PHP with nginx? Does your backend even answer with a response body or a Content-Length header? Provide some configuration files please.