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.

Sign up for GitHub

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

Jump to bottom

Is api:contentNegotation necessary? #1

Open
GoogleCodeExporter opened this issue Aug 3, 2015 · 1 comment
Open

Is api:contentNegotation necessary? #1

GoogleCodeExporter opened this issue Aug 3, 2015 · 1 comment
Labels
auto-migrated

Comments

@GoogleCodeExporter
Copy link 

From Dave Reynolds:

Is the api:contentNegotiation configuration necessary? Why not just allow
dot and _format notation freely?

Original issue reported on code.google.com by [email protected] on 20 Mar 2010 at 4:43
@GoogleCodeExporter
Copy link
Author 

JT: What if they clash? Which takes precedence? Or you do get a 400 error if 
that
happens?

Original comment by [email protected] on 20 Mar 2010 at 4:45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter