Closed Bug 1122714 Opened 9 years ago Closed 9 years ago

url automatically encoded, not send as in urlbar or even in website-source

Categories

(Firefox :: Address Bar, defect, P5)

35 Branch
x86_64
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1121826

People

(Reporter: wtf_ff, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150112203201

Steps to reproduce:

delivered a website with a link: <a href='/abc.php?x[y]=1'>abc</a>



Actual results:

if I hover over the link it appears as entered above in my statusbar.
If I view the source the link is also correct.
If I click on the link or copy it into the clipboard it is urlencoded.


Expected results:

the link must be left as it is! Nothing more. no magic. no "I know it better", no "all strange characters will be transformed to make links work". No no no!
Just leave it to the site-developer.  Why is your opinion better than mine? If I do not want to encode a link, so let me. If this leads to an unworking site, ok, that's my problem, not yours!
Severity: normal → major
Component: Untriaged → Location Bar
Priority: -- → P5
>Just leave it to the site-developer.
The site developers doesn't make the rules, the RFC documents describe how clients and servers should behave.

This is a result of bug 473822 if I understand that bug correctly.
Valetin: Can you confirm that this bug is invalid/wontfix ?
Flags: needinfo?(valentin.gosu)
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(valentin.gosu)
Hello Mr. Versen,

you said the RFC describes how servers __should__ behave. That's right. Maybe I should have encoded my brackets, but if I do not want so, why does ff not allow me to do so? 
And of course the site developer makes the rules. Who else?
Why is mozilla so superior to us site-developers?
If my brackets will lead to broken sites I change them immediately.
But do not change my code!
This is a bug in Firefox. I apologize for the breakage.
You need to log in before you can comment on or make changes to this bug.