LTI - How to get full return url to page

[genadi]

Hi everyone!

Inside basic LTI launch provider application, Is there a way to get a full return url to Canvas page where the LTI launch was done from?

We have a working external tool integration with Canvas of LTI provider application, including deep linking (content item), where users have a button in the rich text editor for embedding media content. The Content item is iframe LTI launch.

The rich text editor can be used in many places such as Canvas Pages, Modules, etc 

The problem is, that inside the LT basic launch I'm having trouble of figuring out the exact url the LTI launch is embedded on. The LTI "launch_presentation_return_url" always contains link to the root url of the course.

For example if the page url is: https://canvas.instructure.com/courses/1510043/pages/test the return url would be: https://canvas.instructure.com/courses/1510043 (same goes for modules, etc).

I've tried looking at variable substitutions, but couldn't find variables for the full url.

Thanks!

[mindcycle]

I would also benefit from an answer to this question. Anyone?

[svickers2]

I am not aware of any mechanism for getting this URL, but am intrigued about the use cases in which it would be needed.  Perhaps if someone could elaborate on what they plan to use the URL for then an alternative solution might be available.

[mindcycle]

I can share my context--may be different from the original author's. I need to pass the actual page name back to the LTI tool so that the page can be logged for the tool itself. In the external tool link add you can get "resource_link_title" but when you launch in an iframe the "resource_link_title" just shows the name of the LTI tool. What I need is to be able to identify the page that the iframe is launched in so that each time the user presses the button it is logged to them as the user and the page that they're on is logged.

[genadi]

In our case, we have a mechanism of notifications to the users that use our LTI and we want to be able to send the users to the right page where the event actually happened, instead only the course url is available which is not a good UX.

The page containing our LTI can contain additional content in addition to the LTI embed, so it's important to be able to send users to the right page.