-
Notifications
You must be signed in to change notification settings - Fork 74
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
Check the usage of $ENV{SCRIPT_NAME} #17
Comments
It would be nice to use |
Using |
Use $ParamObject->ScriptName() instead.
Provided a PR that gets rid of $ENV{SCRIPT_NAME}. The only remaining usage is in ./Kernel/Output/HTML/Templates/Standard/Test.tt . I have no idea where this template is used. |
Issue #17: refrain from using $ENV{SCRIPT_NAME}
PR is merged |
$ENV{SCRIPT_NAME}
is used in several places in the code base. My impression is that these usages are not standard compliant, as SCRIPT_NAME can depend on the webserver setup. In any case it would be nice if $ENV{SCRIPT_NAME} would be inspected in a single central location, e.g. inKernel::System::Web::Request
The text was updated successfully, but these errors were encountered: