HTTPRequest returns a result with OPTIONS but not POST

[fredrossperry]

When I make an HTTP request to my server, which handles CORS, the browser first sends an OPTIONS request, and after that sends my request. A sample program is attached.
But my program receives ResultEvent.RESULT after the OPTIONS, instead of after the POST.
I can see this in the Chrome Dev Tools. I can also see that the POST succeeds and produces expected data.

HTTPTest.zip

[fredrossperry]

... the result data happens to be XML, if that's interesting.

[greg-dove]

I will take a quick look at this shortly. I am using HttpService also

[fredrossperry]

I should mention too that this is meant for Javascript, and not SWF.

[greg-dove]

[Edited to get XML formatting to appear in the comment]
Hi Fred, I took another look at this. It's actually working in terms of the sequence I think, but not decoding the xml to the requested:

service.resultFormat = HTTPService.RESULT_FORMAT_OBJECT;

you can print the result in the result handler with
resultEvent.message.body

instead of resultEvent.result

I switched it to:
RESULT_FORMAT_E4X

and that makes the attempt to create the result as XML
but gives:

 [RPC Fault faultString="Error #1088: The markup in the document following the root element must be well-formed." faultCode="Client.CouldNotDecode" faultDetail="null"]

because the XML seems to be missing a root tag:

<?xml version="1.0" encoding="utf-8"?><success>false</success><retryable>false</retryable><localStatus>SESSION_NO_SUCH_CUSTOMER</localStatus>

There might still be bugs or things to improve, but I think it's working for the most part.

[greg-dove]

Extra info: I think the relevant parts of this are not yet implemented, which may be the cause:

https://github.com/apache/royale-asjs/blob/develop/frameworks/projects/MXRoyale/src/main/royale/mx/rpc/http/AbstractOperation.as#L1038

I can look into this more when I have time, unless someone else gets there first.

[greg-dove]

I added a fix that works for the example provided. Please check the implementation with examples of more complex content if you can and update this issue, preferably with an example of an XML string that does not decode correctly if you see anything that continues to fail. If everything is as it should be, feel free to close the issue.