For those who run into the same issue, the cause is Azure front door. It's doing something, even when waf is disabled.
On Mon, Aug 30, 2021, 6:06 PM James <[email protected]> wrote: > Hrm, thanks. I'll try and isolate it a bit more. Thanks for the reply. > > On Mon, Aug 30, 2021, 5:58 PM Nick Couchman <[email protected]> wrote: > >> On Mon, Aug 30, 2021 at 5:33 PM James <[email protected]> wrote: >> >>> I created a simple loop that is adding 20 or so users. Since I'm using >>> saml, I'm just adding an email address and that's it. I'll randomly get a >>> bad request, but the body of the request looks fine. Same thing when adding >>> a VM connection. Is there some internal rate limit? I catch the exception >>> and rerun the command and move on. I just wanted to see if anyone else has >>> this issue? I see the bad request in the guac log, but nothing explaining >>> why it works if I send the call again. I'm on 1.3.0 Thanks >>> >> >> No, there is no internal rate-limiting. If you're seeing this behavior, >> then you'll want to check and make sure something else along the way isn't >> mangling the packets or HTTP request as it comes across. My immediate >> suspicion would be a reverse proxy, if you're using one (httpd or Nginx), >> but there could be other things, as well. Unless you're doing this >> scripting directly on the server running Tomcat, and directly to Tomcat? >> >> -Nick >> >
