HTTP OPTIONS

[James Mullaney]

Hi all,

Another techy post unfortunately - so if I lost you at the title then probably don't worry about reading any further!

I'm hoping if someone could shed some light on the use of the OPTIONS verb in relation to xAPI - I've been playing around with the tincanapi.com demos today, and noticed all of them call upon xAPI/statements via an OPTIONS call, but this simply isn't defined in the spec as a requirement. I can see the use in having it, but it seems a shame that all the demos simply don't work without an LRS providing an OPTIONS handler, regardless if they have conformed to the spec requirements. Is this oversight on our (LL developers) part, or is this an outdated piece of the specification showing through in older demo pieces?

Thanks,
James

[James Mullaney]

Looking into this more, I'm wondering if this is a browser cross domain handling issue.

[Russell Duhon]

Hi James,

Yes, this is simply a fact of the web, that if you want to support cross domain interaction you need CORS (which, for the operations of the xapi, means OPTIONS). An LRS can be compliant to the spec without CORS support, but the current ecosystem uses it a lot, unfortunately. 

Sincerely,

Russell

Sent from my iPad

--
You received this message because you are subscribed to the Google Groups "Learning Locker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to learning-lock...@googlegroups.com.
To post to this group, send an email to learnin...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[James Mullaney]

Yup, thought as much - not a problem, just means we have to define a few more routes and spit back a load more headers in the right places. Thanks for clarifying Russell.

J