hi Daniele, Where exaclty is a 201 being set as the response code for a PUT. The semantic we are following for restconfig is to have PUT only be used to modify existing resources, therefore only returning a 200.
POST being used to create new resources on the other hand does return a 201.. And it sets the Location header in the response, pointing at the newly created resource. If you look at ReflectiveResource.handlePost() you will see what I mean. That said, we could use PUT to allow for creation of resoures, it is perfectly valid with regard to HTTP. What is your use case here? -Justin Daniele Romagnoli wrote: > Hi list, > I'm doing some work on improving restconfig. > When putting some resource via rest in geoserver, in case everything > goes ok, you will receive a response with a return code = 201 --> > handlePut does this: getResponse().setStatus( Status.SUCCESS_CREATED ); > >From [1] I see that the response should contain some info about the > newly created resource. > This can be achieved by properly setting an Entity in the response, > before setting Status.SUCCESS_CREATED. > Actually, geoserver simply set CREATED in the response without any > additional info. Therefore, there isn't any information about the just > added layer. > Which type of information should we provide within the response? > > Any feedback is welcome. > Regards, > Daniele > > [1]: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html > > -- > ------------------------------------------------------- > Eng. Daniele Romagnoli > Software Engineer > > GeoSolutions S.A.S. > Via Carignoni 51 > 55041 Camaiore (LU) > Italy > > phone: +39 0584983027 > fax: +39 0584983027 > mob: +39 328 0559267 > > > http://www.geo-solutions.it > > ------------------------------------------------------- > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > > > ------------------------------------------------------------------------ > > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
