Feature: raw_query_string()

[epa]

While query_string() provides the current object state as an encoded string, sometimes you want access to the raw query string sent by the user. It would be useful to have a raw_query_string() function giving this. It would return $ENV{QUERY_STRING} but I think it is cleaner to have CGI.pm provide a function for this rather than user code poking around in the env vars directly.

[leejo]

Sounds useful - think you could have a crack at a pull request?

[epa]

Yes tomorrow I will make a pull request.

---

This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com

---

[epa]

What should happen with explicit creation of a CGI object?

 new CGI('foo=bar')

Should raw_query_string return what was passed? Or always follow the env var?

[leejo]

Good question. I think whatever the current object thinks is the current query string is the sensible thing to return. The code already has some checking at object instantiation so most of the logic is probably already there for returning the most recent (correct) query string.

[epa]

That said, look at url_param(). It always returns the parameters in QUERY_STRING, ignoring any parameter string passed at CGI object construction and ignoring any parameter changes set since. So I think this is precedent that raw_query_string() can also just use QUERY_STRING.

[epa]

Thanks for adding this. Sorry my patch got bogged down in the issue of new CGI('foo=bar'). I think your simple approach is fine.