View the original community article here
Last tested: Feb 3, 2021
/login/embed//embed
This is normal!
With our scripts we end up with:
https://your_company.looker.com/login/embed//embed
encoded version:
https://your_company.looker.com/login/embed/%2Fembed
instead of:
https://your_company.looker.com/login/embed/embed
The path is /login/embed/ (that is the route that the server is responding to) the first URL parameter for that route is the target_url (which needs to be url encoded).
The first slash separates the /login/embed from the target url and the second is part of the target url.
So you can think of it like this:/login/embed/<target_url> where the target url is /embed/dashboards (but url encoded)
If you omitted the first one, you wouldn’t be able to log in (because the /login/embed%2Fembed%2Fdashboards route doesn’t exist. And if you omitted the second one (`%2F`) you would successfully log in but when you got redirected after login, you’d go to https://your_company.comembed/dashboards which ALSO wouldn’t work (because `yourcompany.comembed` is not a valid url
company.looker.com//login/embed
This is not normal - these URLs won't work.
This happens when customers include an extra / in their script after the company.looker.com part of the URI - this used to fly in earlier versions, but we updated our routing package somewhere in version 7 so that we now reject invalid URL patterns, so this will now result in a 404. Just remove the extra / to fix the embed path.
This content is subject to limited support.