Skip to main content

Why would a browser do this?

First of all, tell me what's wrong with this picture, then explain to my why a browser would do this?

[21/Nov/2007:16:36:05 --0500] "GET http://esler.is-a-geek.net/labels/Microsoft.html HTTP/1.1" 406 340 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Maxthon)" - "-"

Maxthon is the name of the browser.

Comments

ibneko said…
::wanders in via feedburner::

406 error? Interesting... "The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request."

Not... too sure why a browser would cause that though. By not accepting enough... types of data? Alas, I'm ignorant.
ibneko said…
::wanders in via feedburner::406 error? Interesting... "The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request."Not... too sure why a browser would cause that though. By not accepting enough... types of data? Alas, I'm ignorant.
Joel Esler said…
Let me explain the 406. mod_security threw the 406 back at the requester because the request isn't valid.

It has to do with the actual request itself, not the error code.
Joel Esler said…
Let me explain the 406. mod_security threw the 406 back at the requester because the request isn't valid.It has to do with the actual request itself, not the error code.
Tyler Reguly said…
I can think of a couple of options here...

Both involving proxies

Either someone testing your server to see if it was operating as a proxy... In which case the request you saw is completely valid. As a proxy request takes the form of 'GET http://host/page HTTP/1.1', Maxthon does handle plugins... it could be a plugin for testing sites visited

It could also be that someone changed their anonymous proxy for the day and setup a transparent proxy in their proxy server... Maxthon may not handle transparent proxies and may have tried to treat it as a regular proxy. The transparent proxy would have forwarded based on the host: field, leaving the request intact...
Joel Esler said…
I think Tyler is on it!
Tyler Reguly said…
I can think of a couple of options here... Both involving proxiesEither someone testing your server to see if it was operating as a proxy... In which case the request you saw is completely valid. As a proxy request takes the form of 'GET http://host/page HTTP/1.1', Maxthon does handle plugins... it could be a plugin for testing sites visitedIt could also be that someone changed their anonymous proxy for the day and setup a transparent proxy in their proxy server... Maxthon may not handle transparent proxies and may have tried to treat it as a regular proxy. The transparent proxy would have forwarded based on the host: field, leaving the request intact...
Joel Esler said…
I think Tyler is on it!

Popular posts from this blog

Offset, Depth, Distance, and Within

Without going off the deep-end here and discussing every single Snort rule keyword, I just wanted to touch on a few modifiers that people sometimes misunderstand.  They aren't difficult, and hopefully after this explanation and a few examples, I can clear some of the air around these five modifiers.

The five modifiers that I am talking about are
OffsetDepthDistanceWithinnocaseThese five modifiers are not keywords of themselves, but rather they apply as modifiers to another keyword.  That keyword is "content". The content keyword is one of the easiest pieces of the Snort rules language as all it does is look for a particular string.  So for instance if I wanted to look for the word "joel" within a packet.  A simple:
content:"joel";Would allow me to do that.  The interesting part comes into play when you want to specify where inside of a particular packet you want the string "joel" to be looked for.  If you are running just a plain content ma…

Writing Snort Rules Correctly

Let me start off by saying I'm not bashing the writer of this article, and I'm trying not to be super critical.  I don't want to discourage this person from writing articles about Snort rules.  It's great when people in the Snort community step up and explain some simple things out there.  There are mistakes, it comes with the territory.  If you choose to be one of the people that tries to write Snort rules, you also choose to be someone who wants to learn how to do it better.  That's why I write this blog post, not to bash the writer, but to teach.

I noticed this post today over at the "Tao of Signature Writing" blog, and to be honest I glanced over most of it figuring it was a rehash of things I've already read or things that have already been written from countless people about "Here's how you write Snort rules!".  I scrolled down quickly skimming, not reading at all really, and noticed this part:
Now, let us look at the second questio…

Safari 5.1.4 now available

Safari 5.1.4 now available, fixes issues and improves performance | TUAW - The Unofficial Apple Weblog:


Improve JavaScript performanceImprove responsiveness when typing into the search field after changing network configurations or with an intermittent network connectionAddress an issue that could cause webpages to flash white when switching between Safari windowsAddress issues that prevented printing U.S. Postal Service shipping labels and embedded PDFsPreserve links in PDFs saved from webpagesFix an issue that could make Flash content appear incomplete after using gesture zoomingFix an issue that could cause the screen to dim while watching HTML5 videoImprove stability, compatibility and startup time when using extensionsAllow cookies set during regular browsing to be available after using Private BrowsingFix an issue that could cause some data to be left behind after pressing the "Remove All Website Data" button