-
-
Notifications
You must be signed in to change notification settings - Fork 472
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
Utils::buildWithBaseURLPathdoes not provides a correct url. #464
Comments
any progress with the fix you were working on? |
I am facing the exact same issue. |
I having the same issue. I could push a patch but I have never done that on github. I tried cloning the repo but changing to the 4.0.0 branch just got me a deatched head on a tag with that name. What is the pull request flow for this project? |
Is this the same issue as #249? There's a suggested workaround there (using For example in your case you would use |
Where should i change this? |
Might be a full or partial fix in #581 ? |
Currently i am trying to follow the demo of the library to bootstrap an implementacion.
I am having an issue with the url validation, with the following error being reported:
"The response was received at https://example.domain/main/path/of/url/login.php instead of https://example.domain/main/path/of/url/secondary/path/of/url/login.php?acs"
(the response was sent to "https://example.domain/root/path/of/url/secondary/path/of/url/login.php?acs").
Besides the query string part that I can change or remove, there is an important part of the url not beign taken into account (/secondary/path/of/url/) .
I have identified that Utils::buildWithBaseURLPath does indeed discard a large portion of the $_SERVER['REQUEST_URI'], as array_pop just gets the last part of it.
In my case $_SERVER['REQUEST_URI'] is "/main/path/of/url/secondary/path/of/url/login.php?acs" (the code removes the query string part before passing it to buildWithBaseURLPath.
i would try to fix this in my local copy maybe send a patch, but I don't know what security issues i could introduce.
P.S.
"https://example.domain/root/path/of/url/" is the root of the site not "https://example.domain/root/path/of/url/secondary/path/of/url/", but I am restricted on the route i can use.
The text was updated successfully, but these errors were encountered: