-
-
Notifications
You must be signed in to change notification settings - Fork 475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The response was received at https://{site}/api/sso/acs instead of https://{site}/api/sso/acs #558
Comments
It need to be something else. Have you checked the content inside the SAMLResponse? Maybe there is some extra space or something. |
I've got a similar issue that i've managed to track down to Utils::getSelfRoutedURLNoQuery(). When i've got a 3rd part in my url, it does not work. (/saml/acs/). If I remove the hash from the URL earlier in my application, it works just fine. |
I'm also facing an issue.
My Application is hosted on Azure AppService, using the Code publishing model and PHP 8.1 runtime stack. It is accessible through the Azure Application Gateway. My public domain is linked to the Application Gateway, not in the AppService. Any Fix? |
Finally, I fixed this issue by adding a public domain in the app service and changing the |
Hi!
i'm using v.2.19.1 and I have confusing error -
The response was received at https://{site}/api/sso/acs instead of https://{site}/api/sso/acs
I can't understand - why in error message abolutlely equal string https://{site}/api/sso/acs === https://{site}/api/sso/acs ?
From source -
I read in similar issues that problem can be related to proxy that stands before PHP, but from source code and error message it's not clear is it really the proxy issue.
Does someone faced a similar problem?
How can I debug a real issue that cause to such error?
The text was updated successfully, but these errors were encountered: