You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When i use blueprints with host argument and try to get url with url_for i get an incorrect url - blueprint's host is used as a path, and not as a hostname
1 example returns hostname by like a path 2 example returns hostname and path but it's like a path 3 example return full url, but with no hostname (3 slashes)
Expected behavior
I'm expecting correct urls.
For internal urls - only path returned as stated in route.
For external urls - fully qualified domain name with full path
1 example - / 2 example - /internal 3 example - http://bp.example.com/external
Environment (please complete the following information):
OS: macOS
Version: 19.12.2
Additional context
Can't get correct place, but found some places, where it can be app.py#L829-L832, app.py#L848 (perhaps, blueprint's host should be used, and config's server name as default)
The text was updated successfully, but these errors were encountered:
Tronic
added a commit
to Tronic/sanic
that referenced
this issue
Feb 20, 2020
Describe the bug
When i use blueprints with
host
argument and try to get url withurl_for
i get an incorrect url - blueprint's host is used as a path, and not as a hostnameCode snippet
Output
1
example returns hostname by like a path2
example returns hostname and path but it's like a path3
example return full url, but with no hostname (3 slashes)Expected behavior
I'm expecting correct urls.
For internal urls - only path returned as stated in route.
For external urls - fully qualified domain name with full path
1
example -/
2
example -/internal
3
example -http://bp.example.com/external
Environment (please complete the following information):
Additional context
Can't get correct place, but found some places, where it can be
app.py#L829-L832,
app.py#L848 (perhaps, blueprint's host should be used, and config's server name as default)
The text was updated successfully, but these errors were encountered: