You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found a bug when using the Java apache HTTPClient and setting Content type to the preDefined ContentType.APPLICATION_JSON which set the content type to "application/json; charset=UTF-8". When I use the predefined contentType, I get no targetWorkspace confirmation and the import use the default workspace.
I did not look at the code, but I am suspecting a code that look specificaly for "application/json" since even adding ";" like application/json; does not work.
I also suspect other function to fail supporting charset.
Hi, I am using the importer plugins rest API to add new geodata to geoserver.
According to The documentation:
When I create a new import using a POST on URL geoserver/rest/imports/ with a content-Type like
I specify my import workspace like so
and the return the confirmation of the workspace like so
I found a bug when using the Java apache HTTPClient and setting Content type to the preDefined ContentType.APPLICATION_JSON which set the content type to "application/json; charset=UTF-8". When I use the predefined contentType, I get no targetWorkspace confirmation and the import use the default workspace.
I did not look at the code, but I am suspecting a code that look specificaly for "application/json" since even adding ";" like application/json; does not work.
I also suspect other function to fail supporting charset.
here is the rfc for Content-type
https://www.w3.org/Protocols/rfc1341/4_Content-Type.html
https://www.w3.org/International/articles/http-charset/
The text was updated successfully, but these errors were encountered: