Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the CGI CPAN distribution.

Report information
The Basics
Id: 49454
Status: resolved
Priority: 0/
Queue: CGI

Owner: MARKSTOS [...]
Requestors: ryantate [...]

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

Subject: Documentation bug re -newstyle_urls
Date: Sat, 5 Sep 2009 20:50:19 -0700
To: [...]
From: Ryan Tate <ryantate [...]>
Download (untitled) / with headers
text/plain 891b
The documentation for the -newstyle_urls pragmas includes the following snippet, which is misleading at best: "Semicolon-delimited query strings are always accepted, but will not be emitted by self_url() and query_string() unless the -newstyle_urls pragma is specified. This became the default in version 2.64." In fact, semicolon-delimited query strings *are* emitted even *without* of the -newstyle_urls pragma being specified. This is implied subtly in the second sentence -- it's the default, so you don't have to specify it any more -- but in any case the first sentence is itself incorrect due to the "unless... specified" bit. Better would be something like this: "Semicolon-delimited query strings are always accepted, but will only be emitted by self_url() and query_string() if the -newstyle_urls pragma is in effect. It is in effect by default starting with version 2.64."
Download (untitled) / with headers
text/plain 492b
Thanks for the suggestion, Ryan. This has been patched in my git repo now and will appear in the next release, with credit to you. Here's how the updated docs look: ### ... Semicolon-delimited query strings are always accepted, and will be emitted by self_url() and query_string(). newstyle_urls became the default in version 2.64. =item -oldstyle_urls Separate the name=value pairs in CGI parameter query strings with ampersands rather than semicolons. This is no longer the default.
Subject: Thanks, released
Download (untitled) / with headers
text/plain 160b
The patch for this ticket has now been released in 3.47, and this ticket is considered resolved. Thanks again for you help to improve! Mark

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to