"Page Error" displayed from ContentItemSelectionRequest return post

[kschneider3]

I've been working to get a ContentItemSelectionRequest working in Canvas.   IT works fine with Moodle and in the IMS LTI Tool Consumer emulator .   However, when I post the response the to content_item_return_url  Canvas displays, the error below.   

 

In Chrome developer tools I see ,  is there anyway to get a more detailed response from Canvas so I can resolve this issue?

[kschneider3]

I was omitting the data parameter in my return,  and was hoping that this was it cause, however no go, still get "Page error" with no other information.  I'm scanning now for some other params that canvas might be expecting in the hopes of a resolution.  Any ideas?

[stuart_ryan]

Hi  @kschneider3 ,

If you use the 'Click here to tell us what happened' this will log a Canvas support ticket. They can have a look at the logs that generated on Canvas' side at the time and may be able to rapidly tell you more context surrounding the specific error and why it generated.

It is possible you may have hit a bug (especially as it works fine with Moodle and the emulator), so pulling the logs via Canvas support will probably be the best next step.

I would be very curious to hear what they come back with!

Hope that helps!

Stuart

[kschneider3]

Just opened the support ticket,  I'm as curious as you

[stuart_ryan]

Awesome! Look forward to hearing back from you.

[kschneider3]

Sadly, haven't heard from the support team yet

[kschneider3 · Accepted solution]

Ok, after playing with this more,   we've discovered that Canvas was crapping out when our returned urls were for 127:0.0.1:<a port>    ,  when we ran the code with a real publically accessible DNS it seems to work.

[stuart_ryan]

Hi  @kschneider3 ,

That is great news, I can see how the 127.0.0.1 would have been a problem (as that would only route locally within the machine) it is what is known as the loopback adaptor and will never route beyond a single device.

Glad you were able to get it solved, and thank you for coming back to give us the solution.

Kind Regards,
Stuart