Response Content Type in Swagger

[zuphilip]

Using a non-standard option in the response content type (e.g. + rdf+xml) does not affect the curl action shown below or the request headers.

[kba]

Can you give an example? Apparently a problem like that just crashed the server, would like to reproduce.

[kba]

The bug happens for text/n3, must investigate in infolis/mongoose-jsonld

[zuphilip]

See #20 the example

[kba]

There was some confusion of media types across the rdf processing libraries. Should be fixed now.

[zuphilip]

Yes, now it works to choose a non-standard option in the response content type withouth a crash and the response body will change accordingly.

The response headers and the options in the curl call are not yet fixed (see initial comment). Thus, I will leave that issue open but with low priority.

[kba]

It's a bug in Swagger. Updated the library to the latet version and it's the same error. It doesn't work for the bundled HTML app either (try: http://infolis.gesis.org/infolink/vendor/swagger-ui/dist/index.html). Not much we can do short of digging into the Swagger JS (the Accept header is also wrong).

The important thing is that the requests are sent to the server correctly.

[kba]

It doesn't work on the official demo site either: http://petstore.swagger.io/ with http://infolis.gesis.org/infolink/swagger.json

[zuphilip]

It is confirmed that this is a swagger-ui bug and it was given the tag P2. I guess that means priority.

[kba]

Seems fixed upstream by swagger-api/swagger-ui@8276fbf

[kba]

Yes, swagger-api/swagger-ui#1767 (comment) is fixed and so is this.

[zuphilip]

Yes, I see that the curl command is now fine. Shouldn't the request header change as well? Cf.

[kba]

Yes they should 😒

[zuphilip]

Is that standard field in swagger-ui? I think I haven't seen this in the demo example from swagger-ui itself...

[kba]

Yes, it's a standard field, but it's disabled in the petstore demo. I disabled it here as well.