<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Just notice such build has a special security provider for the authentication from django <a href="https://github.com/GeoNode/geoserver-geonode-ext">https://github.com/GeoNode/geoserver-geonode-ext</a><div><br></div><div>Francesco</div><div> <br><div><div>Il giorno 29/ago/2016, alle ore 15:44, Guillaume Sueur <<a href="mailto:no-reply@neogeo-online.net">no-reply@neogeo-online.net</a>> ha scritto:</div><br class="Apple-interchange-newline"><blockquote type="cite">I'm gonna try with<br><a href="http://build.geonode.org/geoserver/latest/geoserver.war">http://build.geonode.org/geoserver/latest/geoserver.war</a> and see what<br>happens.<br>Thanks for your kind advices<br><br>Guillaume<br>Le 29/08/2016 à 15:40, Francesco Bartoli a écrit :<br><blockquote type="cite">Maybe you can try with the official stable version 2.9.1 of geoserver<br>just making the operations manually with curl and see if the problem is<br>still happening careless of geonode.<br><br>Regards,<br>Francesco<br><br>Il giorno 29/ago/2016, alle ore 15:32, Simone Dalmasso<br><<a href="mailto:simone.dalmasso@gmail.com">simone.dalmasso@gmail.com</a> <<a href="mailto:simone.dalmasso@gmail.com">mailto:simone.dalmasso@gmail.com</a>>> ha scritto:<br><br><blockquote type="cite">Indeed is strange. Try to delete geoserver and the war file and run<br>paver setup again. Let's see how it goes with a new one. (save your<br>data dir if needed)<br><br>2016-08-29 15:28 GMT+02:00 Guillaume Sueur <<a href="mailto:no-reply@neogeo-online.net">no-reply@neogeo-online.net</a><br><<a href="mailto:no-reply@neogeo-online.net">mailto:no-reply@neogeo-online.net</a>>>:<br><br> Hi again,<br><br> It's really weird. It seems that the printing module is correctly<br> activated (geoserver/pdf/info.json sends some content,<br> corresponding to<br> the correct config.yaml file).<br> But it's like the bindings with the REST API is not done. On another<br> instance, if I request<br> localhost:8080/geoserver/rest/printng/render.png<br> I have an empty PNG in return. On this one, I keep having this<br> damn 405<br> error, just because it is not recognized by the REST API I guess.<br><br> Any clue here ? Maybe I should ask the Geoserver mailing list. It's<br> always hard to guess with these cross-software / configuration<br> problems.<br><br> Best regards<br><br> Guillaume<br><br><br> Le 29/08/2016 à 14:06, Simone Dalmasso a écrit :<br><blockquote type="cite">And if you open that url in your browser you get a 405 too?<br><br>In the layer detail page a 405 on /rest/styles is expected and is the<br>correct behavior. But not more than one.<br><br>2016-08-29 13:52 GMT+02:00 Guillaume Sueur <<a href="mailto:no-reply@neogeo-online.net">no-reply@neogeo-online.net</a> <<a href="mailto:no-reply@neogeo-online.net">mailto:no-reply@neogeo-online.net</a>><br><<a href="mailto:no-reply@neogeo-online.net">mailto:no-reply@neogeo-online.net</a><br></blockquote> <<a href="mailto:no-reply@neogeo-online.net">mailto:no-reply@neogeo-online.net</a>>>>:<br><blockquote type="cite"><br> Hi, thanks for your reply,<br><br> Nothing shows up in the log, even in developer logging mode.<br> Anyway, what is strange is that I get a 405 error (method not allowed)<br> and not a 401 (authentication needed). The requested URL is correct<br> though... :<br><br> <a href="http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180">http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180</a><br></blockquote> <<a href="http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180">http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180</a>><br><blockquote type="cite"> <<a href="http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180">http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180</a><br></blockquote> <<a href="http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180">http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180</a>>><br><blockquote type="cite"><br> (auth account and realm are correct too).<br><br> Best regards<br><br> Guillaume<br><br> Le 29/08/2016 à 13:37, Simone Dalmasso a écrit :<br><blockquote type="cite">Hi, try to take a look at the geoserver logs to see if there is a<br>problem with authenticating with geonode or a missing permission<br></blockquote> (but I<br><blockquote type="cite">don't think). It may just be a small misconfiguration in geoserver.<br><br>Hope this helps<br><br></blockquote> <a href="http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse">http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse</a><br></blockquote> <<a href="http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse">http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse</a>><br><blockquote type="cite"> .org%2Cguillaume%2Ccatch22&height=180<br> <<a href="http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse">http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse</a><br></blockquote> <<a href="http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse">http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse</a>><br><blockquote type="cite"> .org%2Cguillaume%2Ccatch22&height=180><br><blockquote type="cite">2016-08-29 12:23 GMT+02:00 Guillaume Sueur<br></blockquote> <<a href="mailto:no-reply@neogeo-online.net">no-reply@neogeo-online.net</a> <<a href="mailto:no-reply@neogeo-online.net">mailto:no-reply@neogeo-online.net</a>><br></blockquote> <<a href="mailto:no-reply@neogeo-online.net">mailto:no-reply@neogeo-online.net</a><br> <<a href="mailto:no-reply@neogeo-online.net">mailto:no-reply@neogeo-online.net</a>>><br><blockquote type="cite"><blockquote type="cite"><<a href="mailto:no-reply@neogeo-online.net">mailto:no-reply@neogeo-online.net</a><br></blockquote></blockquote> <<a href="mailto:no-reply@neogeo-online.net">mailto:no-reply@neogeo-online.net</a>><br><blockquote type="cite"> <<a href="mailto:no-reply@neogeo-online.net">mailto:no-reply@neogeo-online.net</a><br></blockquote> <<a href="mailto:no-reply@neogeo-online.net">mailto:no-reply@neogeo-online.net</a>>>>>:<br><blockquote type="cite"><blockquote type="cite"><br> Hi list,<br><br> I am experiencing a weird problem with geonode and<br></blockquote></blockquote> geoserver<br><blockquote type="cite"> rest API.<br><blockquote type="cite"> Here is the story. I have a bunch of layers in<br></blockquote></blockquote> Geoserver, and<br><blockquote type="cite"> I can<br><blockquote type="cite"> updatelayers from Geonode without any problem, having the<br></blockquote> thumbnails<br><blockquote type="cite"> correctly created in uploaded/thumbs directory, and<br></blockquote></blockquote> correctly<br><blockquote type="cite"> set to<br><blockquote type="cite"> www-data ownership afterwards to avoid any problem when<br></blockquote> updating from<br><blockquote type="cite"> the web interface.<br><br> Then, if I use the "Define Thumbnail" button from the<br></blockquote></blockquote> Layer<br><blockquote type="cite"> Edit Window,<br><blockquote type="cite"> an empty image is created over the previously created<br></blockquote> thumbnail. I dig a<br><blockquote type="cite"> bit into the code trying to locate the issue. It seems it<br></blockquote> comes from<br><blockquote type="cite"> geoserver api which replies to the request emitted in<br> geoserver/helpers.py on line 1687 with :<br><br> Thumbnail created : {'date': 'Mon, 29 Aug 2016<br></blockquote></blockquote> 10:19:56 GMT',<br><blockquote type="cite"> 'status':<br><blockquote type="cite"> '405', 'content-length': '0'<br> , 'allow': 'GET', 'server':<br></blockquote></blockquote> 'Noelios-Restlet-Engine/1.0..8'}<br><blockquote type="cite"><blockquote type="cite"><br> which means that the Method Not allowed error wasn't<br></blockquote></blockquote> caught back<br><blockquote type="cite"><blockquote type="cite"> correctly by geonode who continued the process and<br></blockquote></blockquote> wrote the empty<br><blockquote type="cite"><blockquote type="cite"> content to a new file.<br><br> I just don't understand why I received this 405 HTTP<br></blockquote></blockquote> error in this<br><blockquote type="cite"><blockquote type="cite"> situation, that I have seen working well on other Geonode<br></blockquote> Instances.<br><blockquote type="cite"><br> I've made the installation following the custom<br></blockquote></blockquote> installation<br><blockquote type="cite"> guide last<br><blockquote type="cite"> week, so I guess with some fresh github code.<br><br> Any clue ?<br><br> Best regards<br><br> Guillaume<br> _______________________________________________<br> geonode-devel mailing list<br> <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br></blockquote></blockquote> <<a href="mailto:geonode-devel@lists.osgeo.org">mailto:geonode-devel@lists.osgeo.org</a>><br><blockquote type="cite"> <<a href="mailto:geonode-devel@lists.osgeo.org">mailto:geonode-devel@lists.osgeo.org</a><br></blockquote> <<a href="mailto:geonode-devel@lists.osgeo.org">mailto:geonode-devel@lists.osgeo.org</a>>><br><blockquote type="cite"> <<a href="mailto:geonode-devel@lists.osgeo.org">mailto:geonode-devel@lists.osgeo.org</a><br></blockquote> <<a href="mailto:geonode-devel@lists.osgeo.org">mailto:geonode-devel@lists.osgeo.org</a>><br><blockquote type="cite"> <<a href="mailto:geonode-devel@lists.osgeo.org">mailto:geonode-devel@lists.osgeo.org</a><br></blockquote> <<a href="mailto:geonode-devel@lists.osgeo.org">mailto:geonode-devel@lists.osgeo.org</a>>>><br><blockquote type="cite"><blockquote type="cite"> <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br></blockquote></blockquote> <<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a>><br><blockquote type="cite"> <<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br></blockquote> <<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a>>><br><blockquote type="cite"><blockquote type="cite"> <<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br></blockquote></blockquote> <<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a>><br><blockquote type="cite"> <<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br></blockquote> <<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a>>>><br><blockquote type="cite"><blockquote type="cite"><br><br><br><br>--<br>Simone<br></blockquote> _______________________________________________<br> geonode-devel mailing list<br> <a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br></blockquote> <<a href="mailto:geonode-devel@lists.osgeo.org">mailto:geonode-devel@lists.osgeo.org</a>><br> <<a href="mailto:geonode-devel@lists.osgeo.org">mailto:geonode-devel@lists.osgeo.org</a><br> <<a href="mailto:geonode-devel@lists.osgeo.org">mailto:geonode-devel@lists.osgeo.org</a>>><br><blockquote type="cite"> <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br></blockquote> <<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a>><br><blockquote type="cite"> <<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br></blockquote> <<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a>>><br><blockquote type="cite"><br><br><br><br>--<br>Simone<br></blockquote><br><br><br><br>-- <br>Simone <br>_______________________________________________<br>geonode-devel mailing list<br><a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a> <<a href="mailto:geonode-devel@lists.osgeo.org">mailto:geonode-devel@lists.osgeo.org</a>><br><a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br></blockquote><br></blockquote></blockquote></div><br></div></body></html>