Windows Service and soap response
up vote
0
down vote
favorite
I have a strange problem with a web service on windows server.
I had to implement a web service to respond to a client invoking a method on my server, facilitated by a wsdl file that was provided to me. My method returns a properly formatted soap response, but there is only one problem: for some strange reason, the client receives an xml string with a carriage return (EOL) before the xml tag and a carriage return later, and returns a "The processing instruction target matching" [xX] [mM] [lL] "is not allowed." error, due precisely to those carriage returns.
If I try to call up my service with SoapUi, in fact, in the response window, appears an empty line immediately before <? xml version = "1.0"
and immediately after </ SOAP-ENV: Envelope>.
The validation of SoapUI gives me the error "xml declaration is not well-formed" and the WS-I Profile Conformance Report gives the same error reported by the client above.
If I delete the returns, the validation returns me positive result!
The strange thing is that, by debugging my php code, if I intercept the response after $server->handle(), it appears with no returns !!!! However, this comes to the client with the returns inserted!
Can the web server have something to do with it? I have IIS 7.5.
I'm crazy, can anyone help me? Thank you.
xml soap service response eol
asked Nov 22 at 16:15
user3198834
11
add a comment |
up vote
0
down vote
favorite
I have a strange problem with a web service on windows server.
I had to implement a web service to respond to a client invoking a method on my server, facilitated by a wsdl file that was provided to me. My method returns a properly formatted soap response, but there is only one problem: for some strange reason, the client receives an xml string with a carriage return (EOL) before the xml tag and a carriage return later, and returns a "The processing instruction target matching" [xX] [mM] [lL] "is not allowed." error, due precisely to those carriage returns.
If I try to call up my service with SoapUi, in fact, in the response window, appears an empty line immediately before <? xml version = "1.0"
and immediately after </ SOAP-ENV: Envelope>.
The validation of SoapUI gives me the error "xml declaration is not well-formed" and the WS-I Profile Conformance Report gives the same error reported by the client above.
If I delete the returns, the validation returns me positive result!
The strange thing is that, by debugging my php code, if I intercept the response after $server->handle(), it appears with no returns !!!! However, this comes to the client with the returns inserted!
Can the web server have something to do with it? I have IIS 7.5.
I'm crazy, can anyone help me? Thank you.
xml soap service response eol
asked Nov 22 at 16:15
user3198834
11
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a strange problem with a web service on windows server.
I had to implement a web service to respond to a client invoking a method on my server, facilitated by a wsdl file that was provided to me. My method returns a properly formatted soap response, but there is only one problem: for some strange reason, the client receives an xml string with a carriage return (EOL) before the xml tag and a carriage return later, and returns a "The processing instruction target matching" [xX] [mM] [lL] "is not allowed." error, due precisely to those carriage returns.
If I try to call up my service with SoapUi, in fact, in the response window, appears an empty line immediately before <? xml version = "1.0"
and immediately after </ SOAP-ENV: Envelope>.
The validation of SoapUI gives me the error "xml declaration is not well-formed" and the WS-I Profile Conformance Report gives the same error reported by the client above.
If I delete the returns, the validation returns me positive result!
The strange thing is that, by debugging my php code, if I intercept the response after $server->handle(), it appears with no returns !!!! However, this comes to the client with the returns inserted!
Can the web server have something to do with it? I have IIS 7.5.
I'm crazy, can anyone help me? Thank you.
xml soap service response eol
asked Nov 22 at 16:15
user3198834
11
I have a strange problem with a web service on windows server.
I had to implement a web service to respond to a client invoking a method on my server, facilitated by a wsdl file that was provided to me. My method returns a properly formatted soap response, but there is only one problem: for some strange reason, the client receives an xml string with a carriage return (EOL) before the xml tag and a carriage return later, and returns a "The processing instruction target matching" [xX] [mM] [lL] "is not allowed." error, due precisely to those carriage returns.
If I try to call up my service with SoapUi, in fact, in the response window, appears an empty line immediately before <? xml version = "1.0"
and immediately after </ SOAP-ENV: Envelope>.
The validation of SoapUI gives me the error "xml declaration is not well-formed" and the WS-I Profile Conformance Report gives the same error reported by the client above.
If I delete the returns, the validation returns me positive result!
The strange thing is that, by debugging my php code, if I intercept the response after $server->handle(), it appears with no returns !!!! However, this comes to the client with the returns inserted!
Can the web server have something to do with it? I have IIS 7.5.
I'm crazy, can anyone help me? Thank you.
xml soap service response eol
xml soap service response eol
asked Nov 22 at 16:15
user3198834
11
asked Nov 22 at 16:15
user3198834
11
asked Nov 22 at 16:15
user3198834
11
asked Nov 22 at 16:15
user3198834
11
asked Nov 22 at 16:15
user3198834
11
11
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434851%2fwindows-service-and-soap-response%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
