Bug #11149: URI.parse keeps '?' for query and '#' for fragment even if they are empty

• Status: Rejected
• Assignee: naruse (Yui NARUSE)
• Target version: -
• ruby -v: ruby 2.2.1p85 (2015-02-26 revision 49769) [x64-mingw32]
• Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN

[davispuh (Dāvis Mosāns)]

p = URI.parse('http://example.com/path?query#fragment')
p.query = ''
p.fragment = ''
puts p.to_s

will output "http://example.com/path?#" but I think it should be "http://example.com/path" without '?' and '#'

[naruse (Yui NARUSE)]

• Status changed from Open to Assigned
• Assignee set to naruse (Yui NARUSE)

As URL Standard, current behavior is correct.
https://url.spec.whatwg.org/

But Google Chrome's behavior is like what you say.

I keep watching how W3C/WHATWG decide this behavior.

[davispuh (Dāvis Mosāns)]

Actually yes, I was wrong on this and it is expected behavior.

When one wants without '?' and '#' correct way is to set to nil and not to empty string ''

p.query = nil
p.fragment = nil

[nobu (Nobuyoshi Nakada)]

At least, that test should not be in test_parse, but in test_set_component or others.

[naruse (Yui NARUSE)]

• Status changed from Assigned to Rejected

Chrome also follows the behavior.