Adam Hopkins

That is correct. There is not currently a method to do this manually. It does not sound like it would be a terribly difficult feature to add, and would be...

So, I think the problem is that this counts as a single route definition, and the stream is applied at the definition and not handler. It might be a difficult...

No backport will be needed because 21.12 does not (an will not) purport to support 3.12. It is 3.7-3.10 and that will not change. We probably should add Python versions...

This is still something to do, just not something that we need to release back to the LTS.

I guess it could work if you _manually_ raised `NotFound`. But if the route does not exist, there is no way for Sanic to know which blueprint (and therefore which...

That is not likely something we will introduce since it would require adding default routes to blueprint handlers as catch-all. Which would and could have some bizarre unintended (and difficult...

If that's the case I'd suggest catching the exception with an exception handler and checking if the target path segment is in the current request path.

...

> Not sure why `.strip(':')` was suggested What if the SERVER_NAME is: `//mystie.com` intentionally leaving off the scheme? I think in that case it would erroneously be reported as `http`.

That might not be the case, especially if you wanted to build URLs that had `//` at the beginning without a scheme. Consider your code: ``` { "url": "http://example.com/", "scheme":...