Optimizing nginx mail proxy

Hi everyone, I’m trying to optimize mail-proxy. My performance test is 1 client sends many request to 1 nginx server. This is my current settings: worker_processes auto; worker_rlimit_nofile 10; #error_log /var/log/nginx/error.log debug; #error_log /var/log/nginx/error.log warn;

Re: Mail proxy the destination server by ssl (Postfix)

Thank you for your reply! Posted at Nginx Forum: https://forum.nginx.org/read.php?2,278532,278655#msg-278655 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re[2]: О заголовке content-type

А... голова дырявая. Забыл про types. Спасибо. >Понедельник, 19 февраля 2018, 19:26 +03:00 от Maxim Dounin >: > >Hello! > >On Mon, Feb 19, 2018 at 06:18:52PM +0300, CoDDoC wrote: > >> Доброе время суток! >> >> Есть такой локейшен: >> location ~ "^/img/" { internal; } >>

Fwd: Question about wildcard nginx entry.

-- Forwarded message -- From: bukow bukowiec Date: Mon, Feb 19, 2018 at 9:44 PM Subject: Question about wildcard nginx entry. To: nginx@nginx.org Hello, first time i am writing here, i don't know if my message will go further :) Anyway, can anyone tell

Re: О заголовке content-type

Hello! On Mon, Feb 19, 2018 at 06:18:52PM +0300, CoDDoC wrote: > Доброе время суток! > > Есть такой локейшен: > location ~ "^/img/" { internal; } > > Естественно, прямой запрос 'GET /img/file.jpg' получает 404 > Все хорошо, но нужно вместо стандартной nginx страницы отдать кастомную. > Можно

RE: Clientcertificate authentication only for a single URL

I think this will set the headers only for the login URL but still ask for the certificate on all URLs. And this is not what I need, I only want to have to present a certificate for a single URL Am 19. Februar 2018 16:35:59 MEZ schrieb Jason Whittington : >I

RE: Clientcertificate authentication only for a single URL

I would think "location=" would solve this. What about something like the following? server { listen 443 ssl http2; server_name localhost; ssl_certificate ... ssl_certificate_key ... ssl_session_cache shared:SSL:1m; include

О заголовке content-type

Доброе время суток! Есть такой локейшен: location ~ "^/img/" { internal; } Естественно, прямой запрос 'GET /img/file.jpg' получает 404 Все хорошо, но нужно вместо стандартной nginx страницы отдать кастомную. Можно решать разными способами, я решил попробовать через 'return 404 ' (минимум

Clientcertificate authentication only for a single URL

I need to secure only a single URL on my server by demanding or enforcing client certificate based authentication. My application is called by opening "myapp.local" and if necessary it logs in a user by issuing a call to "myapp.local/login". I can not create a second hostname to do the login,

Re: [PATCH] Limit req: r/h and r/d support

Hello! On Sat, Feb 17, 2018 at 10:07:27PM +0100, Bernhard Reutner-Fischer wrote: > On 16 February 2018 at 17:52, Maxim Dounin wrote: > > >> Limit req: r/h and r/d support > > > Do you use it yourself, or your patch is based on the feature > > requests in question? If yes,

Re: Routing based on ALPN

On 19/02/2018 14:02, Wiktor Kwapisiewicz via nginx wrote: > Hello, > > I'm looking for a way to route traffic on port 443 based on ALPN value > without SSL termination. > > ssl_preread_module [1] does something similar but the only exposed > variable ($ssl_preread_server_name) is for SNI, not

Re: Files still on disc after inactive time

Hello! On Mon, Feb 19, 2018 at 04:38:00AM -0500, Andrzej Walas wrote: > Thanks for your replay I will update nginx I search again. > > Can you anwser on my couple questions: > 1. Can you tell me what happend with downloaded part of files when I have: > 1.1 [error] 16082#0: *1264804 upstream