Ad hoc string searching is a poor substitute for parsing the headers according to RFC 2616 RFC 2616. That is, you should split the request by CRNL line breaks. For the first line, look for three space-separated words. On subsequent lines, look for a field name, followed by a :, followed by the field value.
As currently written, your code could get fooled by a request that looks like:
POST /KFC/CHICKEN_NUGGETS.jpg HTTP/1.0
Host: example.com
or by
GET /wiki/List_of_HTTP_status_codes HTTP/1.0
Host: en.wikipedia.org
What you call the "Query String", the RFC calls the "URI". RFC 3986 defines the Query String to be the part of the URI that follows a ? and precedes a # (if it exists). To avoid confusion, you should use the commonly accepted vocabulary.
Ad hoc string searching is a poor substitute for parsing the headers according to RFC 2616. That is, you should split the request by CRNL line breaks. For the first line, look for three space-separated words. On subsequent lines, look for a field name, followed by a :, followed by the field value.
As currently written, your code could get fooled by a request that looks like:
POST /KFC/CHICKEN_NUGGETS.jpg HTTP/1.0
Host: example.com
or by
GET /wiki/List_of_HTTP_status_codes HTTP/1.0
Host: en.wikipedia.org
What you call the "Query String", the RFC calls the "URI". RFC 3986 defines the Query String to be the part of the URI that follows a ? and precedes a # (if it exists). To avoid confusion, you should use the commonly accepted vocabulary.
Ad hoc string searching is a poor substitute for parsing the headers according to RFC 2616. That is, you should split the request by CRNL line breaks. For the first line, look for three space-separated words. On subsequent lines, look for a field name, followed by a :, followed by the field value.
As currently written, your code could get fooled by a request that looks like:
POST /KFC/CHICKEN_NUGGETS.jpg HTTP/1.0
Host: example.com
or by
GET /wiki/List_of_HTTP_status_codes HTTP/1.0
Host: en.wikipedia.org
What you call the "Query String", the RFC calls the "URI". RFC 3986 defines the Query String to be the part of the URI that follows a ? and precedes a # (if it exists). To avoid confusion, you should use the commonly accepted vocabulary.
Ad hoc string searching is a poor substitute for parsing the headers according to RFC 2616. That is, you should split the request by CRNL line breaks. For the first line, look for three space-separated words. On subsequent lines, look for a field name, followed by a :, followed by the field value.
As currently written, your code could get fooled by a request that looks like:
POST /KFC/CHICKEN_NUGGETS.jpg HTTP/1.0
Host: example.com
or by
GET /wiki/List_of_HTTP_status_codes HTTP/1.0
Host: en.wikipedia.org
What you call the "Query String", the RFC calls the "URI". RFC 3986 RFC 3986 defines the Query String to be the part of the URI that follows a ? and precedes a # (if it exists). To avoid confusion, you should use the commonly accepted vocabulary.
Ad hoc string searching is a poor substitute for parsing the headers according to RFC 2616. That is, you should split the request by CRNL line breaks. For the first line, look for three space-separated words. On subsequent lines, look for a field name, followed by a :, followed by the field value.
As currently written, your code could get fooled by a request that looks like:
POST /KFC/CHICKEN_NUGGETS.jpg HTTP/1.0
Host: example.com
or by
GET /wiki/List_of_HTTP_status_codes HTTP/1.0
Host: en.wikipedia.org
What you call the "Query String", the RFC calls the "URI". RFC 3986 defines the Query String to be the part of the URI that follows a ? and precedes a # (if it exists). To avoid confusion, you should use the commonly accepted vocabulary.
Ad hoc string searching is a poor substitute for parsing the headers according to RFC 2616. That is, you should split the request by CRNL line breaks. For the first line, look for three space-separated words. On subsequent lines, look for a field name, followed by a :, followed by the field value.
As currently written, your code could get fooled by a request that looks like:
POST /KFC/CHICKEN_NUGGETS.jpg HTTP/1.0
Host: example.com
or by
GET /wiki/List_of_HTTP_status_codes HTTP/1.0
Host: en.wikipedia.org
What you call the "Query String", the RFC calls the "URI". RFC 3986 defines the Query String to be the part of the URI that follows a ? and precedes a # (if it exists). To avoid confusion, you should use the commonly accepted vocabulary.
Ad hoc string searching is a poor substitute for parsing the headers according to RFC 2616. That is, you should split the request by CRNL line breaks. For the first line, look for three space-separated words. On subsequent lines, look for a field name, followed by a :, followed by the field value.
As currently written, your code could get fooled by a request that looks like:
POST /KFC/CHICKEN_NUGGETS.jpg HTTP/1.0
Host: example.com
or by
GET /wiki/List_of_HTTP_status_codes HTTP/1.0
Host: en.wikipedia.org
What you call the "Query String", the RFC calls the "URI". RFC 3986 defines the Query String to be the part of the URI that follows a ? and precedes a # (if it exists). To avoid confusion, you should use the commonly accepted vocabulary.