Closed
Bug 283930
Opened 20 years ago
Closed 19 years ago
Use CGI::Util::unescape instead of url_decode
Categories
(Bugzilla :: Bugzilla-General, enhancement, P2)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mkanat, Assigned: mkanat)
References
Details
Attachments
(1 file)
1.50 KB,
patch
|
Details | Diff | Splinter Review |
This is actually only used by query.cgi. Really, instead of using this function, query.cgi's PrefillForm should just use the CGI stuff, and then we should eliminate this function. But for now, we'll just move it.
Assignee | ||
Comment 1•20 years ago
|
||
Actually, CGI already provides a method that does this for us. Why write our own method when everybody already has this method?
Status: NEW → ASSIGNED
Summary: Move url_decode out of CGI.pl → Use CGI::Util::unescape instead of url_decode
Target Milestone: --- → Bugzilla 2.20
Assignee | ||
Comment 2•20 years ago
|
||
Another tiny, tiny, simple, simple patch. CGI.pl is pretty easy to hack away at, so far.
Assignee | ||
Updated•20 years ago
|
Attachment #175705 -
Flags: review?(wurblzap)
Comment 3•20 years ago
|
||
Comment on attachment 175705 [details] [diff] [review] Change url_decode to unescape I think I'm not up to that review. While it's certainly working, and the CGI.pm code has improved since the time of stealing, I'm hesitant to use internal utilities marked as "no public subroutines"... The original reasons for choosing stealing over using may still apply. Opening r?.
Attachment #175705 -
Flags: review?(wurblzap) → review?
Assignee | ||
Comment 4•20 years ago
|
||
Comment on attachment 175705 [details] [diff] [review] Change url_decode to unescape OK, I'll bet justdave knows why we originally changed...
Attachment #175705 -
Flags: review? → review?(justdave)
Assignee | ||
Updated•20 years ago
|
Priority: -- → P2
Assignee | ||
Comment 5•19 years ago
|
||
Comment on attachment 175705 [details] [diff] [review] Change url_decode to unescape OK, maybe glob will know...? :-) He's listed as our CGI.pm guy. :-)
Attachment #175705 -
Flags: review?(justdave) → review?(bugzilla)
like mark i'm in two minds about this one. on the negative side CGI::Util::unescape() is documented as an internal non-public routine, and it would be bad form to use it. i suspect this is the reason why the code was copied into CGI.pl. on the other hand, CGI's unescape adds utf8 support, which we'll eventually require.
Comment 7•19 years ago
|
||
The existing Bugzilla stuff was swiped from CGI.pm before my time. See URI::Escape for a public interface to such a routine. (If that's the only place we're using it, and we haven't already picked up the URI suite via some other dependency, we might as well continue using our own version)
Assignee | ||
Updated•19 years ago
|
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Assignee | ||
Updated•19 years ago
|
Attachment #175705 -
Flags: review?(bugzilla)
Assignee | ||
Comment 8•19 years ago
|
||
Yeah. XML::Parser requires URI, but I can't see anywhere else that we've brought it in in an actually *required* module. And we don't want to use undocumented routines in CGI::Util, definitely, now that I know they're undocumented.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Updated•19 years ago
|
Target Milestone: Bugzilla 2.22 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•