Hmpf. Same problem here :(
def statefulDispatchTable: LiftRules.DispatchPF = {
...
case r...@req(List(api, foo), , PutRequest) = () =
update(req)
...
}
def update(req: Req): LiftResponse = {
for (name - req.paramNames) {
Log.info(name)
Log.info(req.param(name).openOr(empty))
}
Hmpf. I have got the Tomcat PUT problem also.
def statefulDispatchTable: LiftRules.DispatchPF = {
...
case r...@req(List(api, foo), , PutRequest) = () =
update(req)
...
}
def update(req: Req): LiftResponse = {
for (name - req.paramNames) {
Log.info(name)
Crud.
Can someone do a survey of how other JVM web frameworks handle the PUT
inconsistencies on different containers?
On Fri, Feb 5, 2010 at 9:29 AM, Ross Mellgren dri...@gmail.com wrote:
Looking at the Tomcat code, this is explicit. From
org.apache.catalina.connector.Request:
/**
*
CRUD. Yes. Exactly what I'm trying to do, and Tomcat developers are making
it difficult.
I can say that in Jetty 6, they are definitely passed. I don't know
whether they are being stripped in Tomcat deliberately (I hope not) or if
it's a bug. I plan to file a bug report anyway.
I'm running Jetty
If any other proxy includes nginx, then a lot of people!
-
chasc...@munat.com wrote:
CRUD. Yes. Exactly what I'm trying to do, and Tomcat developers are making
it difficult.
I can say that in Jetty 6, they are definitely passed. I don't know
whether they are
Looking at the tomcat code, it seems pretty likely this is a Tomcat-specific
issue.
-Ross
On Feb 5, 2010, at 2:01 PM, Naftoli Gugenheim wrote:
If any other proxy includes nginx, then a lot of people!
-
chasc...@munat.com wrote:
CRUD. Yes. Exactly
Agreed - based on the code, its a systemic issue with Tomcat rather than the
proxy. Consider swapping to another container if that is a viable option...
Cheers, Tim
On 5 Feb 2010, at 19:04, Ross Mellgren wrote:
Looking at the tomcat code, it seems pretty likely this is a Tomcat-specific
On Fri, Feb 5, 2010 at 6:34 PM, David Pollak
feeder.of.the.be...@gmail.com wrote:
Crud.
Can someone do a survey of how other JVM web frameworks handle the PUT
inconsistencies on different containers?
Does S.param map directly to the servletrequest getParameter? If so,
I think the Servlet
On Fri, Feb 5, 2010 at 1:03 PM, Jeppe Nejsum Madsen je...@ingolfs.dkwrote:
On Fri, Feb 5, 2010 at 6:34 PM, David Pollak
feeder.of.the.be...@gmail.com wrote:
Crud.
Can someone do a survey of how other JVM web frameworks handle the PUT
inconsistencies on different containers?
Does
Ha, ha. Brilliant. The writers of the Servlet Spec incorporated the
short-sightedness of the browser makers, who saw no point in PUTs and
DELETEs. Both POST and PUT methods include entities per RFC 2616, so why
is PUT the poor step-sister?
Maybe I'll take another look at virtual hosting in
Yeah, try dumping the Req instance and seeing what is there - if its
empty, then you can be sure its Tomcat causing the problem and not
Lift.
Cheers, Tim
On Feb 4, 8:03 am, Naftoli Gugenheim naftoli...@gmail.com wrote:
Just to double-check, can you acces the form data via the HTTPRequest?
11 matches
Mail list logo
