I am developing an AuthZ module.
While testing using the rate limiting module. I can see rate limiting kick
in for GET requests fine (it's tuned extra low to demonstrate this case):
curl -s -I http://localhost/login?{1..3}
HTTP/1.1 200 OK
Server: nginx/1.21.6
Date: Sun, 04 Dec 2022 16:43:17 GMT
C
Actually analysing the log files of this, it seems the rate limiting module
never kicks in for POST requests, my module just sets the status and bails.
Assuming this is because POST actually needs to write content?
On Sun, 4 Dec 2022 at 16:57, Jeremy Cocks wrote:
> I am developing an AuthZ modul
he location block and just have my module and rate limiting
going without a proxy_pass, it seems to be working fine for all requests.
Thanks!
J
On Sun, 4 Dec 2022 at 19:52, Maxim Dounin wrote:
> Hello!
>
> On Sun, Dec 04, 2022 at 05:29:29PM +0000, Jeremy Cocks via nginx wrote:
>
&
which dictates what phase
a module should be in and its impact?
Obviously, access is quite self-explanatory and not sure how i missed it ;')
On Sun, 4 Dec 2022 at 20:19, Maxim Dounin wrote:
> Hello!
>
> On Sun, Dec 04, 2022 at 08:00:04PM +0000, Jeremy Cocks via nginx wrote:
>
> >
Hello
> and found that it is always redirecting to the first server configured in
the nginx.conf file.
This is expected behaviour when you have not defined a default_server or
you are not sending the appropriate host header in your request (you are
not confirming how things are set in the http cl
Hello!
> I found that port 80 is being used by both task "System" by user
"SYSTEM" for "NT Kernel and System"
with a PID of 4 and also for task "System Idle Process" by user "SYSTEM"
for
"Percentage of time the processor is idle" with a PID of 0.
This is typically the Web Deployment Agent Service
