How to detect rest of c->recv

Hi, I have been working my way around the code base and developing some modules purely for fun[0]. I am now building a core module that acts as an echo server[1]. This is to learn how to actually work with the event loop and clients, etc. One question I have is: How do I know if there is mo

I need help with 403 forbidden

I have just set up nginx on my server to stream video to and retrieve it in an http web page. I have tried everything that I can think of and all the recommendations i could find by Googling but nothing gives me http access th the video stream that is active on the server. I keep adding things

Re: ip address masking

address outside the legitimate range, e.g. 999.9.9.256, so I'll work on fine tuning it soon. But coming up with a succinct _expression_ for ipv6 addresses is proving beyond me for now. On 14 February 2018 at 12:46, Tom <t...@keepschtum.win> wrote:Hi, I'm wondering if anyone has successfully

ip address masking

Hi, I'm wondering if anyone has successfully masked ip addresses in nginx before they are written to a log file. I understand there are reasons why you would and would not do this. Anyway, my config so far, which I believe works for ipv4 addresses, but probably on only a few formats of ipv6 address

Re: OCSP stapling priming and logging

  10.01.2018, 03:02, "Maxim Dounin" :Hello!On Mon, Jan 08, 2018 at 11:38:56PM +1300, Thomas Valentine wrote: I've spent a bit of time setting up my server with SSL, and checkingfor OCSP stapling to be working - couldn't work out why it wasn'tsending the OCSP reply but it's as I was quer

Re: nginx_mail_proxy authenticate to imap_ssl upstream ssl

appreciated,Best regards,Thomas Maxim Dounin schrieb am 15:59 Donnerstag, 20.Juli 2017: Hello! On Thu, Jul 20, 2017 at 09:17:02AM +, tom via nginx wrote: > Hello list, > I configured sucessfully the mail_proxy for nginx 1.10.2 von RHEL7, but > authentication only su

nginx_mail_proxy authenticate to imap_ssl upstream ssl

Hello list, I configured sucessfully the mail_proxy for nginx 1.10.2 von RHEL7, but authentication only succeeds if upstream server which is provided by the auth_http Server is cleartext, e.g. if the auth-server responds 2017/07/20 11:02:47 [debug] 9535#0: *49 mail auth http header: "Auth-Status:

Re: Blocking tens of thousands of IP's

b.com/tmthrgd/ip-blocker-agent . It uses shared memory to store the IP addresses and binary search to iterate through them. It might not work for your circumstance, but it just might. Kind Regards, Tom Thorogood. On Wed, 2 Nov 2016, at 09:13 AM, Cox, Eric S wrote: > Unfortunately much like oth

nginx for Postgres servers

I know nginx is designed to handle web and mail servers. Does it make sense to use to handle multiple (in our case 2) PostgreSQL database servers? Tom Ekberg Senior Computer Specialist, Lab Medicine University of Washington Medical Center 1959 NE Pacific St, MS 357110 Seattle WA 98195 work

auth_basic plain password in html

All, I have setup aut_basic on my nginx webserver, whenever I authenticate the username and password are send as plain text via the html request from my webbrowser, is there an easy solution for this? Or should I switch to the non default nginx_http_auth_digest module? Thanks, Tom

If-Modified-Since and If-None-Match conditionals with X-Accel-Redirect responses ?

Is there any way we can work around this to pass through the ETag and Last-Modified from the backend sending X-Accel-Redirect responses whilst still supporting conditional requests and 304 responses? Thanks, Tom ___ nginx mailing list nginx@nginx.org h

Re: subs filter error

That's the only upstream I'm aware of that works with proxies. On 09/05/2014 23:05, Jonathan Matthews wrote: > On 9 May 2014 13:36, Tom McLoughlin wrote: >> I keep getting this error every time someone loads a page. subs >> filter header ignored, this may be a c

subs filter error

I'm running a TPB proxy on nginx using subs_filter to monetize the proxy with ads, and I keep getting this error every time someone loads a page. subs filter header ignored, this may be a compressed response. while reading response header from upstream, client: xx.xx.xx.xx, server: , request: "GET

Re: 'Primary' domain in server block?

On 7 March 2013 17:06, Francis Daly wrote: > On Thu, Mar 07, 2013 at 09:30:01AM +0000, Tom Barrett wrote: > > Hi there, > Thanks for reading :) > I'm doing some work with PayPal integration. > > How does nginx talk to your PayPal integration system? I think

'Primary' domain in server block?

g' cookie data. I'm looking to explain the situation and make sure we have a nice solution to it. Thanks, Tom ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx