-
Notifications
You must be signed in to change notification settings - Fork 404
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
more IRL and alternate request syntax #1065
Comments
I would expect the alternate request syntax to be supported for 'more' requests. |
The LRS I tested so far reject it all:
It would be great to include |
There's a bit of confusion here due to confusing wording in the spec. When the spec says
That doesn't mean a client using the alternate request syntax must use POST (and the alternate request syntax) all the time, that means when you want to use the alternate request syntax you must use POST. When you're handed a more link, that's considered an opaque link from the LRS that is suitable for GET requests. If you make a POST-burrowed GET to the Statements resource, you should still do a normal GET when following the more link. |
Two points in favour of clarifying this in the spec:
|
Hi, I have a question in regards to statement aggregation and alternative request syntax
This requirement includes
more
IRLs from StatementResult responses?Example:
POST https://lrs.adlnet.gov/xapi/statements/more/ca717872ff5d526bfdd1f9af67e68590?method=GET
with body
would be a valid xAPI request?
(currently returns
405
, method not allowed)The text was updated successfully, but these errors were encountered: