Wesley Wu wrote:
> I changed my post url to "/register1" instead or "/register" and the
> post request was handled properly.
>
> So I think a request to the url "/register" will be always treated as "GET"?
>   
Resin doesn't have any special URL like /register (except the servlet 
j_*). Is there something in the Apache end which is redirecting, or 
changing it, like a filter?

 From the log you sent earlier, it was the front end (Apache) that's 
sending the GET. (There's a log entry for the HTTP method parsing.)

-- Scott
> I scanned the apache log, and the post request was logged correct:
>
> localhost 127.0.0.1 - - [03/Dec/2009:08:18:21 +0800] "POST /register
> HTTP/1.1" 301 346 "http://localhost:889/register/"; "Mozilla/5.0
> (Windows; U; Windows NT 6.0; zh-CN; rv:1.9.1.5) Gecko/20091102
> Firefox/3.5.5 GTB6 (.NET CLR 3.5.30729)" 1000
> localhost 127.0.0.1 - - [03/Dec/2009:08:18:21 +0800] "GET /register/
> HTTP/1.1" 200 9174 "http://localhost:889/register/"; "Mozilla/5.0
> (Windows; U; Windows NT 6.0; zh-CN; rv:1.9.1.5) Gecko/20091102
> Firefox/3.5.5 GTB6 (.NET CLR 3.5.30729)" 77000
>
> But when I looked into resin's access log, I was shocked.
> I found no access log item in it, only the subsequent redirected items:
>
> 127.0.0.1 - - [03/Dec/2009:08:18:21 +0800] "GET /register/ HTTP/1.1"
> 200 8707 "http://localhost:889/register/"; "Mozilla/5.0 (Windows; U;
> Windows NT 6.0; zh-CN; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 GTB6
> (.NET CLR 3.5.30729)"
> 127.0.0.1 - - [03/Dec/2009:08:18:21 +0800] "GET /css/common.css
> HTTP/1.1" 304 - "http://localhost:889/register/"; "Mozilla/5.0
> (Windows; U; Windows NT 6.0; zh-CN; rv:1.9.1.5) Gecko/20091102
> Firefox/3.5.5 GTB6 (.NET CLR 3.5.30729)"
> 127.0.0.1 - - [03/Dec/2009:08:18:21 +0800] "GET /js/humanmessage.js
> HTTP/1.1" 304 - "http://localhost:889/register/"; "Mozilla/5.0
> (Windows; U; Windows NT 6.0; zh-CN; rv:1.9.1.5) Gecko/20091102
> Firefox/3.5.5 GTB6 (.NET CLR 3.5.30729)"
> 127.0.0.1 - - [03/Dec/2009:08:18:21 +0800] "GET /css/style05.css
> HTTP/1.1" 304 - "http://localhost:889/register/"; "Mozilla/5.0
> (Windows; U; Windows NT 6.0; zh-CN; rv:1.9.1.5) Gecko/20091102
> Firefox/3.5.5 GTB6 (.NET CLR 3.5.30729)"
>
>
>
> -Wesley
>
>
> 2009/12/3 Wesley Wu <wumen...@gmail.com>:
>   
>> I think the win32/win64 dlls should be recompiled against the new 
>> modification.
>>
>> 2009/12/3 Wesley Wu <wumen...@gmail.com>:
>>     
>>> I wonder why this happened.
>>> I encountered this in all 4.0.2 versions in my developer machine while
>>> not occurred in production machine.
>>>
>>> I'll do some investigation next.
>>> Thanks Scoot.
>>>
>>> 2009/12/3 Wesley Wu <wumen...@gmail.com>:
>>>       
>>>> I turned it on:
>>>>
>>>> [09-12-03 05:59:44.722] {server--6800-4}
>>>> com.caucho.server.hmux.HmuxRequest handleRequestImpl Hmux[4] start
>>>> request
>>>> [09-12-03 05:59:44.722] {server--6800-4}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[4] r: end of file
>>>> [09-12-03 05:59:44.723] {server--6800-4}
>>>> com.caucho.server.connection.ResponseStream finish Hmux[4] close
>>>> stream
>>>> [09-12-03 05:59:44.723] {server--6800-4}
>>>> com.caucho.server.hmux.HmuxResponseStream flushNext Hmux[4] flush()
>>>> [09-12-03 05:59:44.729] {server--6800-1}
>>>> com.caucho.server.hmux.HmuxRequest handleRequestImpl Hmux[1] start
>>>> request
>>>> [09-12-03 05:59:44.729] {server--6800-1}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[1] r: end of file
>>>> [09-12-03 05:59:44.730] {server--6800-1}
>>>> com.caucho.server.connection.ResponseStream finish Hmux[1] close
>>>> stream
>>>> [09-12-03 05:59:44.730] {server--6800-1}
>>>> com.caucho.server.hmux.HmuxResponseStream flushNext Hmux[1] flush()
>>>> [09-12-03 05:59:44.738] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest handleRequestImpl Hmux[3] start
>>>> request
>>>> [09-12-03 05:59:44.738] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] channel-r 1
>>>> [09-12-03 05:59:44.738] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] U:uri
>>>> /register/
>>>> [09-12-03 05:59:44.738] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] m:method GET
>>>> [09-12-03 05:59:44.739] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] c protocol:
>>>> HTTP/1.1
>>>> [09-12-03 05:59:44.739] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] v server-host:
>>>> localhost
>>>> [09-12-03 05:59:44.739] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] g server-port:
>>>> 889
>>>> [09-12-03 05:59:44.739] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] h 127.0.0.1
>>>> [09-12-03 05:59:44.739] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] i 127.0.0.1
>>>> [09-12-03 05:59:44.740] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] j remote-port:
>>>> 40942
>>>> [09-12-03 05:59:44.740] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] H
>>>> Host=localhost:889
>>>> [09-12-03 05:59:44.740] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] H
>>>> Connection=keep-alive
>>>> [09-12-03 05:59:44.740] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] H
>>>> User-Agent=Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US)
>>>> AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.195.33 Safari/532.0
>>>> [09-12-03 05:59:44.741] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] H
>>>> Referer=http://localhost:889/register/
>>>> [09-12-03 05:59:44.741] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] H
>>>> Cache-Control=max-age=0
>>>> [09-12-03 05:59:44.741] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] H
>>>> Accept=application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>> [09-12-03 05:59:44.741] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] H
>>>> Accept-Encoding=gzip,deflate,sdch
>>>> [09-12-03 05:59:44.742] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] H
>>>> Cookie=userId=bbbeaa; managedFid=a; niceName=%u536B%u65AF%u7406;
>>>> rtime=3; ltime=1259611848411; cnzz_eid=15263584-1258525777-;
>>>> JSESSIONID=aaaYdu83foOsrfeQW7qvs
>>>> [09-12-03 05:59:44.742] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] H
>>>> Accept-Language=zh-CN,zh;q=0.8
>>>> [09-12-03 05:59:44.742] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] H
>>>> Accept-Charset=gb18030,utf-8;q=0.7,*;q=0.3
>>>> [09-12-03 05:59:44.743] {server--6800-3}
>>>> com.caucho.server.hmux.HmuxRequest scanHeaders Hmux[3] Q-r: end of
>>>> request
>>>>
>>>> If I use 8080 port I saw:
>>>>
>>>> [09-12-03 06:00:43.498] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseRequest Http[1] POST /register
>>>> HTTP/1.1
>>>> [09-12-03 06:00:43.498] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseRequest Http[1] Remote-IP:
>>>> 127.0.0.1:61096
>>>> [09-12-03 06:00:43.498] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1] Host:
>>>> localhost:8080
>>>> [09-12-03 06:00:43.498] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1] Connection:
>>>> keep-alive
>>>> [09-12-03 06:00:43.499] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1] User-Agent:
>>>> Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/532.0
>>>> (KHTML, like Gecko) Chrome/3.0.195.33 Safari/532.0
>>>> [09-12-03 06:00:43.499] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1] Referer:
>>>> http://localhost:8080/register
>>>> [09-12-03 06:00:43.499] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1]
>>>> Content-Length: 110
>>>> [09-12-03 06:00:43.499] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1] Cache-Control:
>>>> max-age=0
>>>> [09-12-03 06:00:43.500] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1] Origin:
>>>> http://localhost:8080
>>>> [09-12-03 06:00:43.500] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1] Content-Type:
>>>> application/x-www-form-urlencoded
>>>> [09-12-03 06:00:43.500] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1] Accept:
>>>> application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
>>>> [09-12-03 06:00:43.500] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1]
>>>> Accept-Encoding: gzip,deflate,sdch
>>>> [09-12-03 06:00:43.500] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1] Cookie:
>>>> userId=bbbeaa; managedFid=a; niceName=%u536B%u65AF%u7406; rtime=3;
>>>> ltime=1259611848411; cnzz_eid=15263584-1258525777-;
>>>> JSESSIONID=aaaYdu83foOsrfeQW7qvs
>>>> [09-12-03 06:00:43.513] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1]
>>>> Accept-Language: zh-CN,zh;q=0.8
>>>> [09-12-03 06:00:43.513] {http--8080-1}
>>>> com.caucho.server.http.HttpRequest parseHeaders Http[1]
>>>> Accept-Charset: gb18030,utf-8;q=0.7,*;q=0.3
>>>>
>>>>
>>>> 2009/12/3 Scott Ferguson <f...@caucho.com>:
>>>>         
>>>>> Wesley Wu wrote:
>>>>>           
>>>>>> Another SEVERE issues with this snapshot.
>>>>>>
>>>>>> All "POST" request was dramatically CHANGED to "GET" request.
>>>>>>
>>>>>>             
>>>>> I'm not seeing that behavior. Can you turn on the finer logging and see
>>>>> what filters/includes/forwards are happening?
>>>>>
>>>>> -- Scott
>>>>>           
>>>>>> -Wesley
>>>>>>
>>>>>>
>>>>>> 2009/12/3 Scott Ferguson <f...@caucho.com>:
>>>>>>
>>>>>>             
>>>>>>> Jamison Novak wrote:
>>>>>>>
>>>>>>>               
>>>>>>>> You can ignore this. After further investigation, the developer in 
>>>>>>>> charge of the app says that it's returning a similar error under 
>>>>>>>> Tomcat, which he claims it was not before. There must be something 
>>>>>>>> else going on.
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>> Thanks for the update. The tests I added for the most recent changes
>>>>>>> should have covered large-file posts as well, but there's always a
>>>>>>> chance some case was missing.
>>>>>>>
>>>>>>>               
>>>>>>>> Thanks for the snapshot, though. Shiny new toys are always fun...
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>> Yep. We did some important refactoring for 4.0.2 that had been put off
>>>>>>> for ages, but unfortunately exposed holes in the QA tests. (Of course,
>>>>>>> now we have the new tests, so there's a silver lining.)
>>>>>>>
>>>>>>> -- Scott
>>>>>>>
>>>>>>>               
>>>>>>>> -----Original Message-----
>>>>>>>> From: resin-interest-boun...@caucho.com 
>>>>>>>> [mailto:resin-interest-boun...@caucho.com] On Behalf Of Jamison Novak
>>>>>>>> Sent: Wednesday, December 02, 2009 2:16 PM
>>>>>>>> To: General Discussion for the Resin application server
>>>>>>>> Subject: Re: [Resin-interest] new Resin 4.0 snapshot
>>>>>>>>
>>>>>>>> Thanks, Scott. The snapshot doesn't seem to have fixed the related 
>>>>>>>> error that we were seeing with one of our apps.
>>>>>>>>
>>>>>>>> If we submit a form with a long list of files in a text box, we get 
>>>>>>>> the same error according to Grails (I don't see anything special in 
>>>>>>>> Resin's "finer" logging, though). If the list of files in the field is 
>>>>>>>> shortened, we get no error. Could this be a related POST size error?
>>>>>>>>
>>>>>>>> We're trying to troubleshoot the app itself on our end, but there's 
>>>>>>>> not much in the logs to go by.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Jamie
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: resin-interest-boun...@caucho.com 
>>>>>>>> [mailto:resin-interest-boun...@caucho.com] On Behalf Of Scott Ferguson
>>>>>>>> Sent: Wednesday, December 02, 2009 1:08 PM
>>>>>>>> To: resin-interest@caucho.com
>>>>>>>> Subject: [Resin-interest] new Resin 4.0 snapshot
>>>>>>>>
>>>>>>>> There's a new Resin 4.0 snapshot with additional fixes for the 
>>>>>>>> hmux/forwarding issues.
>>>>>>>>
>>>>>>>> -- Scott
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> resin-interest mailing list
>>>>>>>> resin-interest@caucho.com
>>>>>>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> resin-interest mailing list
>>>>>>>> resin-interest@caucho.com
>>>>>>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> resin-interest mailing list
>>>>>>>> resin-interest@caucho.com
>>>>>>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>> _______________________________________________
>>>>>>> resin-interest mailing list
>>>>>>> resin-interest@caucho.com
>>>>>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>> _______________________________________________
>>>>>> resin-interest mailing list
>>>>>> resin-interest@caucho.com
>>>>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>>>>
>>>>>>
>>>>>>             
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> resin-interest mailing list
>>>>> resin-interest@caucho.com
>>>>> http://maillist.caucho.com/mailman/listinfo/resin-interest
>>>>>
>>>>>           
>
>
> _______________________________________________
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest
>
>   




_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to