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
Overriding MIME Types doesn't work #370
Comments
Hi @vadim-hleif, thanks for reporting this! I can confirm this behaviour, and based on how I wrote it, it makes sense - the URL query string gets parsed long before the I'd tend to agree with you that it's a bug, since the express purpose of the My initial feeling on precedence is: path extension, This wouldn't help you in the case of the GitHub URL provided, since the An option in the GitHub case is to use their contents API. It's a bit of a kludge but it's more predictable:
Either way, |
@hairyhenderson Hello, could you release this changes soon? Thank you! |
My apologies @vadim-hleif! I'll see if I can get a release out today or this weekend. |
Works
type of content the same as in
Content-Type
response header:gomplate -d config=http://private-30833-vadimhleif.apiary-mock.com/yaml -i '{{ (ds "config").name }}'
Don't work
type of content not the same as in
Content-Type
response header, overriding MIME doesn't work:gomplate -d config=http://private-30833-vadimhleif.apiary-mock.com/text -i '{{ (ds "config").name }}'
don't work, expectedgomplate -d config=http://private-30833-vadimhleif.apiary-mock.com/text?type=application/yaml -i '{{ (ds "config").name }}'
don't work, not expectedwhat
It may be helpful. for example, for github api:
https://raw.githubusercontent.com/cloudposse/geodesic/master/README.yaml
why
text/plain
content-Type and gomplate can't parse yamlreferences
The text was updated successfully, but these errors were encountered: