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

Unsupported informat='multipart/form-data' #21

Open
Katsivelisp opened this issue Jun 22, 2016 · 7 comments
Open

Unsupported informat='multipart/form-data' #21

Katsivelisp opened this issue Jun 22, 2016 · 7 comments

Comments

@Katsivelisp
Copy link

Hello,

invoking the e-publishing service at http://api.freme-project.eu/current/e-publishing/html returns the following error, even in the API Documentation page:
{ "exception": "eu.freme.common.exception.BadRequestException", "path": "/e-publishing/html", "message": "Unsupported informat='multipart/form-data'. The following serialization format values are acceptable: rdf-xml, application/xml, application/ld+json, n-triples, application/x-turtle, application/json, turtle, n3, application/rdf+xml, csv, text/xml, text/turtle, text/html, application/json+ld, xml, text/comma-separated-values, json, text, text/n3, application/x-openoffice, json-ld, application/n-triples, text/plain, application/x-xliff+xml", "error": "Bad Request", "status": 400, "timestamp": 1466584161257 }
Running the same call on api-dev seems to be working. I have provided both valid metadata and a .zip file.

@pheyvaer
Copy link
Contributor

So I think that this has something to do with the documentation page then, and not necessarily the service itself?

@Katsivelisp
Copy link
Author

No, when I run the corresponding cURL command directly on http://api.freme-project.eu, I get the same error.

@pheyvaer
Copy link
Contributor

but you said that 'Running the same call on api-dev seems to be working.'?

@Katsivelisp
Copy link
Author

Katsivelisp commented Jun 22, 2016

Yes, so:
http://api.freme-project.eu/current/e-publishing/html returns the error pasted above.
http://api-dev.freme-project.eu/current/e-publishing/html works fine.

EDIT: You can use the cURL from #22 and switch the URL from dev to production.

@pheyvaer
Copy link
Contributor

pheyvaer commented Jun 22, 2016

The e-Publishing service hasn't changed since the latest versions. @ArneBinder could you have a look at this? (Unless, this is something for @jnehring, but he is not available I thought)

@ArneBinder ArneBinder self-assigned this Jun 22, 2016
@ArneBinder
Copy link
Contributor

This is caused by a modification in the internalization filter. I adapted the changes in e-Publishing a month ago (registering supported mime types), so I'm not sure, why it was not released so far. When @jnehring does the next release of e-Publishing, this will be fixed in the live version.

@ArneBinder ArneBinder removed their assignment Jun 22, 2016
@fsasaki
Copy link

fsasaki commented Jun 22, 2016

Thanks, Arne. Is there a way for us to do the release or do we have to wait
until Jan is back?

2016-06-22 15:24 GMT+02:00 ArneBinder [email protected]:

This is caused by a modification in the internalization filter. I adapted
the changes in e-Publishing a month ago (registering supported mime types),
so I'm not sure, why it was not released so far. When @jnehring
https://github.com/jnehring does the next release of e-Publishing, this
will be fixed in the live version.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABH5Aj6BuZZCJGynvCJjYF5D9c4wcy0rks5qOTeZgaJpZM4I7h2K
.

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

4 participants