Hello,
we are using xajax 0.5 beta 4 on our webpage for checking the existance of an username in the registrationprocess for example.
Currently we are testing our page with SSL which is configured a bit "special" as the ssl-connection ends on our loadbalancer(LB). The LB then adds the following line to the request-header: "X-Forwarded-Protocol:https" and the request is forwarded via normal http to our webserver.

The strange thing now is, that - when called via SSL - the xajax-request looks like this: "OPTIONS filethatisrequested.html" instead of "POST filethatisrequested.html". This causes the request to fail as the server does not respond or does not respond in the expected way. When called over "normal" HTTP the same code works fine and the request is made via POST.

Do you have any hints why xajax is confused and send the OPTIONS-request instead of POST? We have set the defaultRequestMethod to GET instead, but with SSL the request is still made with "OPTIONS".

Thanks alot for your help.