-
Notifications
You must be signed in to change notification settings - Fork 391
Conversation
Thanks for yout PR! Well, we could add this at next major version of package, but this is Albert's decision. I wouldn't go with it for now |
Is it the transition from 'public_path' to 'document_root' standing in the way of accepting the fix to the security issue? |
"Low priority" for a security issue? |
yes, that way we had a BC that would force us to release the fix in a major version |
Fair enough, it's now removed. This should be included in a release as soon as possible, if the proposed solution is indeed acceptable. Thank you. |
Thanks @kanarip . I'll prepare the release this week. Good job |
We are definitely not using a custom route exception handler, albeit we are using a fallback route, but another project that doesn't use such a fallback route is used to reproduce below; Prepare the verification as follows;
|
Oh I see. You're not using nginx in front of swoole, are you? |
No. Neither NGINX nor Apache nor any other "proxying" engine that secretly does more than just proxy. |
This pull request also brings the used terminology of "public_path" in line with Swoole upstream's "document_root".
Reproduce and validate with, repeating
../
as many times as is necessary to get to your/
top level directory: