Stop emails to me
On Tue, Jul 14, 2020, 6:13 AM Maxim Dounin wrote:
> Hello!
>
> On Tue, Jul 14, 2020 at 04:25:46AM -0400, salmanpskply wrote:
>
> > I have a requirement where when proxied response error code is 401
> > (condition #1) and response body has text "SAML Token Expired" (condition
>
On Tue, Jul 14, 2020 at 09:55:04AM -0400, siva.pannier wrote:
Hi there,
> Output from the server when client initiated the connection is..
> #
> javax.net.ssl.SSLHandshakeException: no cipher suites in common
That suggests that the ssl client (nginx) and the ssl server (you
Extremely sorry, I mentioned the wrong port in that post.. Actually I am
using the correct port number..
Client (Windows + non SSL):8091 ==> Nginx host (ubuntu vm+ SSL redirection)
==> TCP server (Windows + SSL enabled)
TCP server listening on 8091
Nginx Server listening on 8091
Client makes ca
On Tue, Jul 14, 2020 at 08:28:35AM -0400, CarstenK. wrote:
Hi there,
> we use nginx plus for caching and purge URLs automatic by our Shopsystem. In
> some times we have a lot of URLs to purge and need for every (sometimes
> wildcard purge) an extra request.
>
> Is it possible to purge a list of
On Tue, Jul 14, 2020 at 02:20:54AM -0400, redflag wrote:
Hi there,
I don't have an answer for you, but...
> i am writing a new Nginx filter module , the main issue is that when i try
> to read the request body it turn out to be null, is there a way to READ THE
> BODY??
>
> i found an already e
Thank you
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,288683,288693#msg-288693
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Mon, Jul 13, 2020 at 02:57:34PM -0400, siva.pannier wrote:
Hi there,
> https://docs.nginx.com/nginx/admin-guide/security-controls/securing-tcp-traffic-upstream/
>
> My TCP (non-ssl) client is able to hit the TCP Server (SSL enabled) via the
> Nginx (proxy_ssl) but buffered reader gets back on
Hello!
On Tue, Jul 14, 2020 at 04:25:46AM -0400, salmanpskply wrote:
> I have a requirement where when proxied response error code is 401
> (condition #1) and response body has text "SAML Token Expired" (condition
> #2), I need to intercept it and redirect to refresh token API.
>
> I could do it
Hello,
we use nginx plus for caching and purge URLs automatic by our Shopsystem. In
some times we have a lot of URLs to purge and need for every (sometimes
wildcard purge) an extra request.
Is it possible to purge a list of urls in one request?
regards
Carsten
Posted at Nginx Forum:
https://fo
I have a requirement where when proxied response error code is 401
(condition #1) and response body has text "SAML Token Expired" (condition
#2), I need to intercept it and redirect to refresh token API.
I could do it partially where only error code 401 is considered. Not able to
find a way to rea
10 matches
Mail list logo