Why does a Soap response is blocked(I see 200 OK but not response message) in FF due to
(Reason: CORS header 'Access-Control-Allow-Origin' missing).
But not through SoapUI from the same machine(computer).
Is it that FF is blocking the response. If so , how can I make it work.
I used this to send Soap request through FF.
Related
I am implementing a server that will receive a POST request from the client, through an API, in the header it has a callback URL where we need to send a PUT message for this callback URL later. This is to implement an Async API.
In resume the flow is:
Client --- POST ---> Server
Client <-- 202 --- Server
Client <-- PUT/CallbackURL --- Server
Client --- 200 ---> Server
Can I make Postman having a Stub server capable to receive this callback and do a 200 response?
Thanks, #adsc!
Postman has Mock Servers: learning.postman.com/docs/postman/mock-servers/setting-up-mock
Your comment fixes my problem and I didn't find it before.
https://learning.postman.com/docs/postman/mock-servers/setting-up-mock/
Is SOAP end-point over HTTP expected to return any status code except 200 and 500? I have a SOAP end-point that has some business logic to reject requests when there are too many of them. I wonder what is the correct HTTP response code in this case - 500 or 429? The SOAP specification seems vague to me:
SOAP HTTP follows the semantics of the HTTP Status codes for
communicating status information in HTTP. For example, a 2xx status
code indicates that the client's request including the SOAP component
was successfully received, understood, and accepted etc.
In case of a SOAP error while processing the request, the SOAP HTTP
server MUST issue an HTTP 500 "Internal Server Error" response and
include a SOAP message in the response containing a SOAP Fault element
(see section 4.4) indicating the SOAP processing error.
In short SOAP uses HTTP/HTTPS as a transport. It is not bound to HTTP/S. SOAP can also use SMTP and JMS as a transport. Yes you can do SOAP via email.
The 200 and 500 error codes mentioned is just the standard way of letting SOAP know that the message contains a successful or failed SOAP request. Thus I would use 500 with the error logged in the standard SOAP fault.
Which HTTP Method is used to send SOAP messages?
I guess, if you are working at the servlet level,you could define the HTTP method(would there still be restrictions?).
But if all that is hidden, and I'm using a simple JAX WS webservice, which HTTP method would(should??) the request and response messages have?
I think JAX-WS and most other implementations use post for transmitting requests
you can verify it by capturing the request in TCP IP monitor
I log the http request on server, but I don't have the HTTP Header.
How can I log the HTTP Header on server?
I do this : http://wiki.eclipse.org/Jetty/Tutorial/Sifting_Logs_with_Logback
My jetty's version is 8.1.3.
Thanks
Vince
I am trying to setup very simple WSO2 ESB Proxy service. While using it, I am getting HTTP 202 response back and WSO2 ESB is not doing anything with the request beside logging it. Here is the background of my setup
My service implementation is using SOAP 1.2 over Http 1.1. When my client opens the connection to the server, it fires first request and asks for keep-alive connection. The ESB passes the request to the actual implementation and sends response back with transfer-encoding as chunked. So far it works as desired.
After the initial request response exchange, my client submits several requests in parallel and I get HTTP 202 responses for all of them. Looking at logs, it seems ESB is not sending the request to the actual implementation ever.
Is there something that I am doing wrong? How do I fix it?
What happens in this scenario is that your subsequent requests are hitting the main sequence of the WSO2 ESB. That is why you can only see a log for those requests. As you have already narrowed down this happens due to the jsessionId attached to the URL. To overcome this issue you can create a REST API with URL pattern to match the correct URL path. Please refer the following documentation.
https://docs.wso2.com/display/ESB481/Creating+APIs