Re[2]: addEventlistener question
Jacob Kjome <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Organization | Springfield Nuclear Plant |
| Message-ID | <[email protected]> |
Hello Christian, Wednesday, March 05, 2003, 10:33:52 AM, you wrote: CC> Ok, so now on second thought, I started wondering about this. If I look in CC> ApplicationGateway, it looks to me like doPut is in fact enabled - it should CC> route to the same handleDefault() method as doGet or doPost. So I'm CC> wondering why PUT didn't work. I wonder if it is a function of the appserver CC> you are using perhaps? CC> ever curious, CC> Christian I think it is a function of the browser. Unless I'm mistaken, no current browser supports HTTP PUT. They only support GET and POST. That is the reason that when using, for instance, the Tomcat manager app, you can't "deploy" your .war via the browser, only "intall" or upload a .war file using HTTP POST (in recent Tomcat-4.1.x versions). The only way to do this (without writing your own program) is by using the Catalina Ant manager "deploy" task. I'm not sure we should even have HTTP PUT enabled? In fact, it would have cleared up this issue from the get-go. We have to understand the behavior of HTTP PUT as far as how parameters are passed before we allow its use. We are all famililar with POST and GET and should probably limit Barracuda to that until we actually understand how to support PUT. The other option is to detect the client and ask if it actually supports PUT. If not, we return an error page stating the lack of client support. Jake