Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[server] Feature request: Allow custom routing #3377

Closed
jepotter1-archive opened this issue Nov 2, 2018 · 3 comments
Closed

[server] Feature request: Allow custom routing #3377

jepotter1-archive opened this issue Nov 2, 2018 · 3 comments
Labels
documentation Improvements or additions to documentation enhancement outdated

Comments

@jepotter1-archive
Copy link

Long story short

I am creating a package based on aiohttp (https://github.com/jwinnie/maglev). This package implements custom routing behaviors based on middleware.

Expected behaviour

I am able to disable the routing mechanism and jump straight to the handle function for all routes.

Actual behaviour

I currently use a workaround which probably impacts performance:

app.add_routes([web.route("*", "/{tail:.*}", handle)])
@aio-libs-bot
Copy link

GitMate.io thinks the contributor most likely able to help you is @asvetlov.

Possibly related issues are #689 ([Feature Request] Provide a JsonResponse class), #1618 (allow HEAD requests to default routes), #3259 (What takes request.task so long to complete (server)?), #2816 (Feature request: add functionality to retrieve the the server certificate in a client request), and #1528 (Can't GET or POST request for custom ports with URL).

@aio-libs-bot aio-libs-bot added documentation Improvements or additions to documentation enhancement labels Nov 2, 2018
@asvetlov
Copy link
Member

asvetlov commented Nov 2, 2018

Please consider low-level API: https://aiohttp.readthedocs.io/en/stable/web_lowlevel.html#

@asvetlov asvetlov closed this as completed Dec 1, 2018
@lock
Copy link

lock bot commented Dec 1, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Dec 1, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Dec 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation enhancement outdated
Projects
None yet
Development

No branches or pull requests

3 participants