Hide Forgot
Description of problem: fpaste returns a case-sensitive URL. To the best of my knowledge, URLs are not case sensitive. I've tested this with fpaste and found that the same paste is returned regardless of character case. Generating case sensitive URLs adds no benefit to the user, and unnecessarily introduces ambiguity. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. fpaste foo.file Actual results: resource http://fpaste.org/Il10O is generated Expected results: resource http://fpaste.org/il10o is generated Additional info:
hi Pete, This bug isn't against fpaste. It's actually against fpaste-server. fpaste just spews out what the server returns. Reassigning to correct component. Thank you for reporting the bug :) Ankur
Actually RFC only specifies 'scheme' (protocol) case : scheme should be lowercase and, if it's not, should be considered as if it was. Hostnames are case insensitive either, but the url-path can be case sensitive, depending of the server implementation. Windows web servers are not case sensitive, and most of linux webserver just are. Limiting the URL to lowercase chars could also limit the number of simultanesous pastes being available at the same time. If there's no paste "slot" available, I'm sure user will see no benefit in *that*. Also, User, most of the time, just copy-pastes the fpaste URL in mail/IRC/IM/whatever. User almost never types the URL, so discomfort is limited. Now, considering your observations on fpaste.org/ABC being the same paste than fpaste.org/abc, a Good Question would be : can fpaste server generate case-collisions ?
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.