Databases
StackOverflow2013
Postsdbo
POWhy is my Spring service returning any content type requested by client?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy is my Spring service returning any content type requested by client?
    primarykey
    data
    text
    <p>I have a Spring rest service using Spring 3.1.0.RELEASE. Here is the relevant code for the service call in question:</p> <pre><code>@RequestMapping(value="/{var1}", method=RequestMethod.GET, produces="application/json") @ResponseBody public String getSomeStuff(@PathVariable final String var1) { return myJsonString; } </code></pre> <p>If I call this using the following curl command, it happily returns me my json string with a content-type of application/xml whereas I would expect a 406 based on the Spring 3.1 docs:</p> <pre><code>curl -v -H "Accept: application/xml" http://localhost:8080/MyServiceSite/myvalue </code></pre> <p>There is no extra configuration in my app for this service (no serialization), I am returning raw json with no post-processing for the service configured. I'm certain I have missed something, can anyone point out anything I may have missed?</p> <p>Edit: Here is the <a href="http://static.springsource.org/spring/docs/current/spring-framework-reference/html/mvc.html#mvc-ann-requestmapping-produces" rel="nofollow">documentation</a> I was looking at when attempting to get this working. Specifically section 16.3.2.5. My code is very similar except that their code looks like it assumes config setup to let Spring handle serialization. Perhaps the produces does not work when bypassing the Spring serialization?</p> <p>Edit: I changed my expectation for the response code. A 415 would indicate I was sending improper content in my request body whereas 406 is proper for having an accept header that doesn't jive with the content type of the server.</p> <p>Anyway, I have changed this method do return a Map and added config for it to serialize to json and now if I send an invalid content type from the client I get the proper 406 response. It seems that maybe the "produces" setting is ignored when the output of the method is not being serialized.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmockobject
    1. USmockobject
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy is my Spring service returning any content type requested by client?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy is my Spring service returning any content type requested by client?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy is my Spring service returning any content type requested by client?
      1. USTomasz Nurkiewicz
      1. VTFavorite
    1. COPerhaps you could answer your own question with the modified code and the applicable configuration so someone viewing in the future could benefit.
      singulars
      1. POWhy is my Spring service returning any content type requested by client?
      1. USdigitaljoel
    2. COI will if I can't figure out a way to do it without turning on the serialization. The data I have is already serialized so it would be unfortunate if I had to de-serialize it and re-serialize it to get the proper behavior. So I am still looking for any other way to get this working.
      singulars
      1. POWhy is my Spring service returning any content type requested by client?
      1. USmockobject
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload