From: "jhawthorn (John Hawthorn) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "jhawthorn (John Hawthorn)" <noreply@ruby-lang.org>
Subject: [ruby-core:118900] [Ruby master Bug#20686] URI::HTTPS can build URI with blank, invalid host
Date: Mon, 19 Aug 2024 22:59:23 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-109469.20240819225923.53421@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20686.20240819194059.53421@ruby-lang.org>
Issue #20686 has been updated by jhawthorn (John Hawthorn).
Interestingly RFC2396_PARSER seems to allow nil for a host but not empty string, so the newer behaviour is at least more consistent. It does seem like we are missing some expected validation here though.
```
> URI::HTTPS.new(nil, nil, "", nil, nil, nil, nil, nil, nil, URI::RFC2396_Parser.new, true)
/Users/jhawthorn/.rubies/ruby-3.3.2/lib/ruby/3.3.0/uri/generic.rb:601:in `check_host': bad component(expected host component): (URI::InvalidComponentError)
from /Users/jhawthorn/.rubies/ruby-3.3.2/lib/ruby/3.3.0/uri/generic.rb:640:in `host='
...
>> URI::HTTPS.new(nil, nil, nil, nil, nil, nil, nil, nil, nil, URI::RFC2396_Parser.new, true)
=> #<URI::HTTPS >
```
----------------------------------------
Bug #20686: URI::HTTPS can build URI with blank, invalid host
https://bugs.ruby-lang.org/issues/20686#change-109469
* Author: ronricardo (Roniece Ricardo)
* Status: Open
* ruby -v: 3.4.0+
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
In Ruby 3.4.0+, calling `URI::HTTPS.build(host: "")` does not raise `URI::InvalidComponentError` as expected. Instead, it returns `#<URI::HTTPS https://>`
I think this was introduced in [this PR](https://github.com/ruby/uri/pull/90).
## Steps to Reproduce
### 1. Environment:
- **Ruby Version:** 3.4.0+
### 2. Steps:
- Open an IRB session.
- Run:
```ruby
URI::HTTPS.build(host: "")
```
### 3. Expected Behavior:
- `URI::InvalidComponentError` should be raised due to the invalid empty `host` component.
### 4. Actual Behavior:
- Returns `#<URI::HTTPS https://>` without raising an error.
### Ruby 3.1.4:
```ruby
irb(main):008:0> RUBY_VERSION
=> "3.1.4"
irb(main):009:0> URI::HTTPS.build(host:"")
/home/vscode/.rbenv/versions/3.1.4/lib/ruby/3.1.0/uri/generic.rb:601:in `check_host': bad component(expected host component): (URI::InvalidComponentError)
```
### Ruby 3.4.0:
```ruby
irb(…):015> RUBY_VERSION
=> "3.4.0"
irb(...):016> URI::HTTPS.build(host:"")
=> #<URI::HTTPS https://>
```
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
next prev parent reply other threads:[~2024-08-19 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 19:41 [ruby-core:118894] " ronricardo (Roniece Ricardo) via ruby-core
2024-08-19 20:04 ` [ruby-core:118895] " jeremyevans0 (Jeremy Evans) via ruby-core
2024-08-19 22:45 ` [ruby-core:118899] " jhawthorn (John Hawthorn) via ruby-core
2024-08-19 22:59 ` jhawthorn (John Hawthorn) via ruby-core [this message]
2024-08-19 23:46 ` [ruby-core:118901] " jeremyevans0 (Jeremy Evans) via ruby-core
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-109469.20240819225923.53421@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).