I wonder how our configuration looks like in detail. What's configured per server and what per location level?
And, you didn't use "/aoo" as the URI pattern, do you?
Do you really need dynamic error page mapping or have you tried to configure it statically using the QS_ErrorPage directive?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You could redirect requests using QSRedirectIf based on thresholds you configure for the QSSrvConn and QSIPConn variables. But this won't be a hard "connection" limitation as you need to wait for the client sending a request.
Therefore the QSLocRequestLimit and QSClientEventRequestLimi directives together with QSErrorPage would be the most obvious solution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
~~~
~~~Hi, I have set limited concurrent access, when over the limit, visitor will see error page like this
I tried at this setting
SetEnvIf Request_URI /app QS_ErrorPage=http://mytestserver.com/error.html
But NOT success, any other settings I can try, or my setting is wrong ?
Thanks
Last edit: Calvin Wong 2022-07-13
I wonder how our configuration looks like in detail. What's configured per server and what per location level?
And, you didn't use "/aoo" as the URI pattern, do you?
Do you really need dynamic error page mapping or have you tried to configure it statically using the QS_ErrorPage directive?
MY CONFIG IS VERY SIMPLE LIKE THIS:
Anything wrong ? I am not familiar with Apache and firtime using mod_qos, hope you can help newbie and give some simple expample
Thank you very much
You can't configure an error page for directives denying on connection level (there is no response without a request).
Thanks,
when over the limit, redirect to customized error page
anyway to make this work ?
You could redirect requests using QSRedirectIf based on thresholds you configure for the QSSrvConn and QSIPConn variables. But this won't be a hard "connection" limitation as you need to wait for the client sending a request.
Therefore the QSLocRequestLimit and QSClientEventRequestLimi directives together with QSErrorPage would be the most obvious solution.