Hello!
> One of the bcrypt scheme main properties is that it allows to
> control number of rounds, and thus control hashing speed. With
> low number of rounds it is reasonably fast. For example, with 2^5
> rounds (default used by htpasswd) it takes about 4 milliseconds
> here on a test box:
Hallo Matthias!
Thanks for your post, it brought me on the right track! Additionally, I
found the MediaWiki ShortURL Builder at https://shorturls.redwerks.org/.
From there I added a few more {deny all;} rules.
And the result seems to be working now!
Thanks again ... und viele Grüße
Jörg
Posted
Hello,
anyone know how to help me?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,273081,275116#msg-275116
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Fri, Jun 23, 2017 at 01:24:19PM +, Lukas Tribus wrote:
> Hello,
>
>
> > In nginx there is no native support for bcrypt passwords as
> > produced by Apache's htpasswd. On the other hand, nginx can use
> > all password schemes supported by crypt(3) on your OS. Many
> > operatin
Hello,
> In nginx there is no native support for bcrypt passwords as
> produced by Apache's htpasswd. On the other hand, nginx can use
> all password schemes supported by crypt(3) on your OS. Many
> operating systems do support bcrypt-encrypted passwords in
> crypt(3), and if Apache's varia
Hello!
On Thu, Jun 22, 2017 at 06:26:50PM -0400, Dwight Marzolf wrote:
> We have an installation of nginx 1.10.3 in which we are using an htpasswd
> file that contains bcrypt encyrpted passwords. This is a file that is used
> by multiple apps that require authentication. Everything I am reading
Hi Maxim,
Thanks for your prompt answer !
That's exactly what I'm using currently, but was thinking if there is
some more elegant/performance-effective way of doing this thing.
Regards
On 06/23/2017 03:09 PM, Maxim Dounin wrote:
Hello!
On Fri, Jun 23, 2017 at 02:31:37PM +0300, Gryzli Bug
Hello!
On Fri, Jun 23, 2017 at 02:31:37PM +0300, Gryzli Bugbear wrote:
> I have the following working scheme:
>
> Client --> Nginx [caching] --> Apache [backend]
>
>
> Sometime the backend returns headers, which I want to modify before
> nginx caching engine decides how to treat them. One suc
Hello everybody,
I have the following working scheme:
Client --> Nginx [caching] --> Apache [backend]
Sometime the backend returns headers, which I want to modify before
nginx caching engine decides how to treat them. One such example is when
backend returns Vary: header.
I want to achi
So as you guys said: it's a normal behavior of nginx and the problem is how
can I monitor response time exactly?because, when I request a static link (a
jpeg i.e), it take about 3s to completely download, but request_time still
0.000, and because it's a HIT request so I dont have upstream_response
10 matches
Mail list logo