[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 524
  • Last Modified:

HTTP Protocol Question regarding message types HEAD and OPTIONS

I have found some rather disturbing messages built into the HTTP protocol like
DELETE /page.html
PUT /page.html
I say disturbing because it is a security nightmare isn't it?
I  had thought that the HEAD /page.html   HTTP/1.1  
request command would be harmless enough but then I came across:
http://apache-range-exploit.com/

There is also supposed to be an OPTIONS request message that also fails to work on Apache servers.
Can anyone comment on this odd RFC 1226?
0
Robert Silver
Asked:
Robert Silver
  • 2
1 Solution
 
mccarlIT Business Systems Analyst / Software DeveloperCommented:
> I have found some rather disturbing messages built into the HTTP protocol like DELETE, PUT

Well, POST and even GET can be just as dangerous, it depends on how they are used!


> I say disturbing because it is a security nightmare isn't it?

That's why you have security built in to the application, and the HTTP protocol even provides for this if desired. It is not mandatory though because the protocol is designed to be applicable across a wide range of applications. Some of those may be totally within a trusted environment, in which if excessive security is forced would result is less efficient operations, for example.


> I  had thought that the HEAD /page.html   HTTP/1.1  
request command would be harmless enough but then I came across

The example that you cite is an issue with the "implementation" of the protocol within one particular product, it is not an issue with the protocol itself.


> There is also supposed to be an OPTIONS request message that also fails to work on Apache servers.

Ok!


> Can anyone comment on this odd RFC 1226?

That RFC doesn't seem to have anything to do with the rest of your post, is that the one you meant to quote?
0
 
Dave BaldwinFixer of ProblemsCommented:
Try this from http://www3.ntu.edu.sg/home/ehchua/programming/howto/Apache_HowToConfigure.html .

<LimitExcept GET POST>
   Order deny,allow
   Deny from all
</LimitExcept>

Open in new window


Apparently, DELETE and PUT require a 'handler' to function.
0
 
Dave BaldwinFixer of ProblemsCommented:
In IIS, each handler can have the 'verbs' set that are passed to it.  Most Microsoft services only see "GET, POST, HEAD, DEBUG" and some only see GET and POST.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now