[
https://jira.jboss.org/jira/browse/JBIDE-6281?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-6281:
------------------------------------------
Ok, Lucas, I'm a bit confused on this one.
1) Is it a hard and fast rule that JAX-RS POST/PUT requests can't include request
params in the URL? Or is it just that this particular web service doesn't handle it?
2) Do you want me to return the same info as the TCP/IP monitor? I can get the request
headers back (like the TCP/IP monitor) and stick those in the response header list in the
tester?
--Fitz
[tester] REST POST/PUT request params should be sent within request
body
------------------------------------------------------------------------
Key: JBIDE-6281
URL:
https://jira.jboss.org/jira/browse/JBIDE-6281
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.next
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
Fix For: 3.2.next
-open tester
-test following service:
Type: JAX-RS
Method POST
Service URL:
http://www.webservicex.net/BibleWebservice.asmx/GetBibleWordsByChapterAnd...
request parameters: BookTitle=John, chapter=3 and Verse=2
request headers: Content-Type=application/x-www-form-urlencoded, Content-Length=32
request body: empty
-configure monitor
-and invoke the service
=> no response comes back from the server and TCP/IP monitor shows only:
POST
/BibleWebservice.asmx/GetBibleWordsByChapterAndVersechapter=2&BookTitle=John&verse=2
HTTP/1.1
content-type: application/x-www-form-urlencoded
content-length: 32
User-Agent: Java/1.6.0_18
Host: localhost:8077
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
which means that there's wrong request sent to the server
problem here is that request params should be sent with request body and not as part of
url, so we should either do not take request params into account for POST/PUT requests or
send them within request body and automatically set content-type(?) and content-length
headers for the request
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira