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
environment case-insensitive warning painful #372
Comments
That sounds like some unintended side effects of #355 Those changes are specifically made to clear up any ambiguity around having both I think we need to restrict this check to env vars that we care about it and not warn in other cases. Pull request certainly welcome. :) |
I'll append a simple diff for your consideration, essentially duplicating the "we don't care about this envvar" tests from the bottom of the loop. I can't easily generate a PR, sorry. Also, the logic of that for loop is not exactly clear to me (sorry again), so I expect you'll want to adjust the change in some wa or another. Please consider this contribution trivial/uncopyrightable/public domain/do as you like :). Thanks for considering.
|
Thanks @kberry! |
This may help if changes to fix libwww-perl#372 are done.
This may help if changes to fix libwww-perl#372 are done.
Before doing changes to fix libwww-perl#372 it is good to have a complete test coverage of env_proxy().
Before doing changes to fix libwww-perl#372 it is good to have a complete test coverage of env_proxy().
Before doing changes to fix libwww-perl#372 it is good to have a complete test coverage of env_proxy().
Before doing changes to fix #372 it is good to have a complete test coverage of env_proxy().
As of LWP::UserAgent 6.52, and perhaps somewhat earlier, it started to complain about case-insensitive "clashes" of environment variables when env_proxy was set. Even for environment variables that have nothing to do with LWP, and even when the environment is case sensitive (e.g., Unix :). This is frustrating, since it newly requires "cleaning" things which, it seems to me, LWP should not be complaining about. For example, say we have the trivial tryua.pl:
and then run
There is output:
(Naturally, in practice the issue is not with explicitly-specified envvars like this, but case-varying envvars that I have set in my environment for reasons unrelated to LWP.)
At least for me, tt would be nice if either LWP wouldn't complain on case-sensitive systems, or wouldn't complain about envvars that it doesn't ever read, or at least had an option to suppress these checks. Thanks for considering.
The text was updated successfully, but these errors were encountered: