-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WCS 2.0.1 compliance test (te2) has problem in wcs2:post-xml-req5 #119
Comments
Thank you for reporting. There might be a connection to issue #55. Is it possible to provide a test service instance so that we can analyze the TEAM Engine logging? |
Full error message: Indeed, it seems that the HTTPParser cannot handle the response of your service. |
@greatzzk My findings are that the response has probably a syntax issue. According to this RFC, there needs to be an empty line after the header section of each (multi)-part. Example of a response from your server:
I did some test with multipart libraries and they could read the response only after I manually added an empty line after the header section:
|
@greatzzk Please let us know when you have fixed the issue on your server. |
Thanks!! We will change accordingly and retest against TE2 |
@ghobona @bpross-52n |
Thank you reporting back. We will take a look at your results. |
@greatzzk My tests show that there is still no new line after the header section of the second (inline tiff) part. That is the reason the parsing still fails. |
@bpross-52n thanks for analyzing the problem and apparently we have added that blank line as showing in the screenshot above. |
@greatzzk Yes, the parser can now read the first part (GML), but the second part still looks like this:
when it should look like this:
|
@bpross-52n thanks. we will fix accordingly and retest here |
it passed all wcs 2.0.1 post-xml test on TE2 now. We added a blank line between each header and body inside the multi-part response. |
request and failure msg is like:
but it works on my side with a proper response. It looks to me that the test fails to parse the returned multipart tiff
The text was updated successfully, but these errors were encountered: