| reply to Windstream
Re: Our Response to Redirect Service Concerns I also wanted to add that the sheer fact the URL was transformed, being carefully re-written, from the URI passed to 'www.google.com' once again discredits what you've said entirely.
It's not surprising, you've refused to answer the questions from multiple Windstream subscribers concerning this.
Allow me to get technical.
When a user performs a search using the Firefox search bar against Google HTTP/1.1 is used with an HTTP method of GET against Google. The following URI is constructed:
q=[search critera]
ie=[encoding]
oe=[encoding]
aq=
rls=[browser]
So, when I search against Google I pass ?q= for my search term.
When this is redirected to searchredirect.windstream.net the URI is transformed, with the ?q= parameter being extracted. Your site uses this URI structure:
search=[search criteria]
src=[interger value, likely points to an RDBMS based on HTTP_REFERER]
So you see, you're absolutely, with confidence, not disclosing the truth. For this behavior to occur you would have to be using an MITM proxy or DPI; either way you are inspecting Layer 7 traffic, extracting the ?q= URI string passed to Google, and either transparently or via HTTP 302 redirecting customers to your searchredirect.windstream.net
You got caught, red handed, and have been fabricated mis-truths from the start.
How HTTP/1.1 GET against /search?q=my_search_term becomes /search.php?search=my_search_term without some form of Layer 7 is impossible. This CANNOT be NXDOMAIN.
Clearly you're not disclosing the full details or hiding behind careful sentence structure and semantics. |
