-
Notifications
You must be signed in to change notification settings - Fork 1.4k
v1_parser: use URI#open instead of URI.open #4854
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
Conversation
04a12fb to
0254d7e
Compare
daipom
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
It appears to me that v1parser can recognize Windows absolute paths (C:/foo).
Can't we just use u.open?
|
Thanks. Indeed, seems it recognize Windows path. |
Signed-off-by: Shizuo Fujita <[email protected]>
0254d7e to
d6aa891
Compare
daipom
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
**Which issue(s) this PR fixes**: Fixes # **What this PR does / why we need it**: By [CodeQL documentation](https://codeql.github.com/codeql-query-help/ruby/rb-non-constant-kernel-open/), it is safer to avoid using `URI.open`. This is similar with fluent#4848 **Docs Changes**: **Release Note**: Signed-off-by: Shizuo Fujita <[email protected]> Signed-off-by: Kentaro Hayashi <[email protected]>
**Which issue(s) this PR fixes**: Fixes # **What this PR does / why we need it**: By [CodeQL documentation](https://codeql.github.com/codeql-query-help/ruby/rb-non-constant-kernel-open/), it is safer to avoid using `URI.open`. This is similar with fluent#4848 **Docs Changes**: **Release Note**: Signed-off-by: Shizuo Fujita <[email protected]> Signed-off-by: Kentaro Hayashi <[email protected]>
**Which issue(s) this PR fixes**: Fixes # **What this PR does / why we need it**: By [CodeQL documentation](https://codeql.github.com/codeql-query-help/ruby/rb-non-constant-kernel-open/), it is safer to avoid using `URI.open`. This is similar with fluent#4848 **Docs Changes**: **Release Note**: Signed-off-by: Shizuo Fujita <[email protected]> Signed-off-by: Kentaro Hayashi <[email protected]>
**Which issue(s) this PR fixes**: Fixes # **What this PR does / why we need it**: By [CodeQL documentation](https://codeql.github.com/codeql-query-help/ruby/rb-non-constant-kernel-open/), it is safer to avoid using `URI.open`. This is similar with fluent#4848 **Docs Changes**: **Release Note**: Signed-off-by: Shizuo Fujita <[email protected]> Signed-off-by: Kentaro Hayashi <[email protected]>
**Which issue(s) this PR fixes**: Fixes # **What this PR does / why we need it**: By [CodeQL documentation](https://codeql.github.com/codeql-query-help/ruby/rb-non-constant-kernel-open/), it is safer to avoid using `URI.open`. This is similar with fluent#4848 **Docs Changes**: **Release Note**: Signed-off-by: Shizuo Fujita <[email protected]> Signed-off-by: Kentaro Hayashi <[email protected]>
…4921) **Which issue(s) this PR fixes**: Backport #4854 Fixes # **What this PR does / why we need it**: By [CodeQL documentation](https://codeql.github.com/codeql-query-help/ruby/rb-non-constant-kernel-open/), it is safer to avoid using `URI.open`. This is similar with #4848 **Docs Changes**: **Release Note**: Signed-off-by: Shizuo Fujita <[email protected]> Signed-off-by: Kentaro Hayashi <[email protected]> Co-authored-by: Shizuo Fujita <[email protected]>
Which issue(s) this PR fixes:
Fixes #
What this PR does / why we need it:
By CodeQL documentation, it is safer to avoid using
URI.open.This is a false positive, so there is no impact on Fluentd.
(Because URI.parse checks the uri in advance.)
This is similar with #4848
Docs Changes:
Release Note: