-
-
Notifications
You must be signed in to change notification settings - Fork 119
Move construction of proxied path to method #74
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
Conversation
That method isn't actually getting the path it's only pre-processing the path before returning. Can you give me some cases where having this method would be relevant? Thanks! |
Hey @seocam So, what I was trying to do was to proxy rabbitmq's management web UI/API. Rabbitmq has a concept of vhosts, which are present in the API paths. The default rabbitmq vhost is However, what ended up being proxied was Unfortunately, as far as I can tell, django's uri parsing happens on the unescaped data, so the path matched by the regex in the url conf would always contain By moving the preprocessing of I know it isn't the cleaner solution, do you have any suggestions as to how else I could have achieved my goal of properly proxying |
|
Thanks for the clarification @dimrozakis! What about calling this method |
To make it easier for subclasses to modify behavior.
@seocam sure thing. I renamed the function as suggested, squashed and pushed. |
To make it easier for subclasses to modify behavior.