Query String for Simple GET requests

"Bob Joneson" <[email protected]> Sat, 3 Jan 2009 00:59:02 -0600
Newsgroups gmane.linux.upnp-sdk.general
Message-ID <[email protected]>
--===============5739924253217572977==
Content-Type: multipart/alternative; 
	boundary="----=_Part_130898_1041031.1230965942959"

------=_Part_130898_1041031.1230965942959
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I've been scouring the code a bit, and am looking for a good way to get at
the query string (variable / value pairs) which "may" accompany an HTTP GET
request to the mini web server. I believe that parser_parse_requestline
would theoretically retain this as part of url_str.

I do realize that these query strings on simple GETS don't really fall into
the upnp spec, but there a few vendor implementations (i.e. Microsoft) which
have chosen to.... "extend" functionality with odd hacks such as the query
string.

I'm happy to plug away on the code, but was curious if there were any
suggestions for a starting point. Thanks in advance for any help.

------=_Part_130898_1041031.1230965942959
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I&#39;ve been scouring the code a bit, and am looking for a good way to get at the query string (variable / value pairs) which &quot;may&quot; accompany an HTTP GET request to the mini web server. I believe that parser_parse_requestline would theoretically retain this as part of url_str. <br>
<br>I do realize that these query strings on simple GETS don&#39;t really fall into the upnp spec, but there a few vendor implementations (i.e. Microsoft) which have chosen to.... &quot;extend&quot; functionality with odd hacks such as the query string. <br>
<br>I&#39;m happy to plug away on the code, but was curious if there were any suggestions for a starting point. Thanks in advance for any help. <br>

------=_Part_130898_1041031.1230965942959--


--===============5739924253217572977==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------

--===============5739924253217572977==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
UPnP-SDK-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/upnp-sdk-discuss

--===============5739924253217572977==--