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

Why aren't dotted values allowed for resource ids? #86

Open
qur opened this issue May 15, 2014 · 2 comments
Open

Why aren't dotted values allowed for resource ids? #86

qur opened this issue May 15, 2014 · 2 comments

Comments

@qur
Copy link

qur commented May 15, 2014

goweb seems to always assume that a . means a file extension - but when using a controller this doesn't really make sense.

e.g. DELETE /something/10.0.0.1 would call somethingController.Delete("10", ctx) - which seems really very wrong ...

@tylerstillwater
Copy link
Contributor

goweb allows you to override the codec being used by passing a different extension (.xml,.json).

Obviously this is a problem for you. Do you have any thoughts on a way to handle this differently?

@qur
Copy link
Author

qur commented May 27, 2014

How about adding a flag to HttpHandler that can cause WebContext to use a new Path constructor that doesn't split out the extension instead of NewPath? Whilst it might be nice to be able to select on a per Controller basis, I can't see a practical way to accomplish that, and don't myself need to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants