[GeoNode-devel] Thumbnail update fails
Guillaume Sueur
no-reply at neogeo-online.net
Mon Aug 29 07:35:22 PDT 2016
Sure, it is not really complicated.
Just deploy the war, and see what you get at
curl -u login:password -X POST
http://localhost:8080/geoserver/rest/printng/render.png
if you have an ugly dump of PNG content (like �PNG
IHDJ�Y0�IDATx���1 �0� �DB���)
it means that the rest print bindings works.
If you don't get anything, add the -v option to cURL, the response
header should tell you :
< HTTP/1.1 405 Method Not Allowed
< Allow: GET
< Date: Mon, 29 Aug 2016 14:34:39 GMT
* Server Noelios-Restlet-Engine/1.0..8 is not blacklisted
< Server: Noelios-Restlet-Engine/1.0..8
< Transfer-Encoding: chunked
Best regards
Guillaume
Le 29/08/2016 à 16:22, Alessio Fabiani a écrit :
> Hello all,
> geoserver.war is 2.7.x version.
>
> I'll take a look at the 2.9.x one. Maybe it's a security configuration
> issue on the REST module.
>
> Can you please write here how exactly I can reproduce the issue?
>
>
> Best Regards,
> Alessio Fabiani.
>
> ==
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/it488V for more information.
> ==
>
> Ing. Alessio Fabiani
> @alfa7691
> Founder/Technical Lead
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 331 6233686
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio
> stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti,
> copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento
> contrario ai principi dettati dal D.Lgs. 196/2003.
>
>
>
> The information in this message and/or attachments, is intended solely
> for the attention and use of the named addressee(s) and may be
> confidential or proprietary in nature or covered by the provisions of
> privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data
> Protection Code).Any use not in accord with its purpose, any disclosure,
> reproduction, copying, distribution, or either dissemination, either
> whole or partial, is strictly forbidden except previous formal approval
> of the named addressee(s). If you are not the intended recipient, please
> contact immediately the sender by telephone, fax or e-mail and delete
> the information in this message that has been received in error. The
> sender does not give any warranty or accept liability as the content,
> accuracy or completeness of sent messages and accepts no responsibility
> for changes made after they were sent or for other risks which arise as
> a result of e-mail transmission, viruses, etc.
>
> ---------------------------------------------------------------------
>
>
> On Mon, Aug 29, 2016 at 4:13 PM, Guillaume Sueur
> <no-reply at neogeo-online.net <mailto:no-reply at neogeo-online.net>> wrote:
>
> Hey, I think I've got something here !
> If I use the geoserver.war from
> http://build.geonode.org/geoserver/latest/
> <http://build.geonode.org/geoserver/latest/>, it's all fine, but if
> I take
> the geoserver-2.9.x.war, it doesn't work...
>
>
>
> Le 29/08/2016 à 15:54, Francesco Bartoli a écrit :
> > Just notice such build has a special security provider for the
> > authentication from django https://github.com/GeoNode/geoserver-geonode-ext
> <https://github.com/GeoNode/geoserver-geonode-ext>
> >
> > Francesco
> >
> > Il giorno 29/ago/2016, alle ore 15:44, Guillaume Sueur
> > <no-reply at neogeo-online.net <mailto:no-reply at neogeo-online.net>
> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>>> ha scritto:
> >
> >> I'm gonna try with
> >> http://build.geonode.org/geoserver/latest/geoserver.war
> <http://build.geonode.org/geoserver/latest/geoserver.war> and see what
> >> happens.
> >> Thanks for your kind advices
> >>
> >> Guillaume
> >> Le 29/08/2016 à 15:40, Francesco Bartoli a écrit :
> >>> Maybe you can try with the official stable version 2.9.1 of
> geoserver
> >>> just making the operations manually with curl and see if the
> problem is
> >>> still happening careless of geonode.
> >>>
> >>> Regards,
> >>> Francesco
> >>>
> >>> Il giorno 29/ago/2016, alle ore 15:32, Simone Dalmasso
> >>> <simone.dalmasso at gmail.com <mailto:simone.dalmasso at gmail.com>
> <mailto:simone.dalmasso at gmail.com <mailto:simone.dalmasso at gmail.com>>
> >>> <mailto:simone.dalmasso at gmail.com
> <mailto:simone.dalmasso at gmail.com>>> ha scritto:
> >>>
> >>>> Indeed is strange. Try to delete geoserver and the war file and run
> >>>> paver setup again. Let's see how it goes with a new one. (save your
> >>>> data dir if needed)
> >>>>
> >>>> 2016-08-29 15:28 GMT+02:00 Guillaume Sueur
> >>>> <no-reply at neogeo-online.net <mailto:no-reply at neogeo-online.net>
> <mailto:no-reply at neogeo-online.net <mailto:no-reply at neogeo-online.net>>
> >>>> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>>>:
> >>>>
> >>>> Hi again,
> >>>>
> >>>> It's really weird. It seems that the printing module is
> correctly
> >>>> activated (geoserver/pdf/info.json sends some content,
> >>>> corresponding to
> >>>> the correct config.yaml file).
> >>>> But it's like the bindings with the REST API is not done. On
> another
> >>>> instance, if I request
> >>>> localhost:8080/geoserver/rest/printng/render.png
> >>>> I have an empty PNG in return. On this one, I keep having this
> >>>> damn 405
> >>>> error, just because it is not recognized by the REST API I
> guess.
> >>>>
> >>>> Any clue here ? Maybe I should ask the Geoserver mailing
> list. It's
> >>>> always hard to guess with these cross-software / configuration
> >>>> problems.
> >>>>
> >>>> Best regards
> >>>>
> >>>> Guillaume
> >>>>
> >>>>
> >>>> Le 29/08/2016 à 14:06, Simone Dalmasso a écrit :
> >>>>> And if you open that url in your browser you get a 405 too?
> >>>>>
> >>>>> In the layer detail page a 405 on /rest/styles is expected and
> is the
> >>>>> correct behavior. But not more than one.
> >>>>>
> >>>>> 2016-08-29 13:52 GMT+02:00 Guillaume Sueur
> >>>>> <no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>
> <mailto:no-reply at neogeo-online.net <mailto:no-reply at neogeo-online.net>>
> >>>>> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>>
> >>>>> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>
> >>>> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>>>>:
> >>>>>
> >>>>> Hi, thanks for your reply,
> >>>>>
> >>>>> Nothing shows up in the log, even in developer logging mode.
> >>>>> Anyway, what is strange is that I get a 405 error (method not
> >>>>> allowed)
> >>>>> and not a 401 (authentication needed). The requested URL is
> correct
> >>>>> though... :
> >>>>>
> >>>>>
> 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>
> >>>>
> <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>>
> >>>>>
> <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>
> >>>>
> <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>>>
> >>>>>
> >>>>> (auth account and realm are correct too).
> >>>>>
> >>>>> Best regards
> >>>>>
> >>>>> Guillaume
> >>>>>
> >>>>> Le 29/08/2016 à 13:37, Simone Dalmasso a écrit :
> >>>>>> Hi, try to take a look at the geoserver logs to see if there is a
> >>>>>> problem with authenticating with geonode or a missing permission
> >>>>> (but I
> >>>>>> don't think). It may just be a small misconfiguration in
> geoserver.
> >>>>>>
> >>>>>> Hope this helps
> >>>>>>
> >>>>>
> 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>
> >>>>
> <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>>
> >>>>> .org%2Cguillaume%2Ccatch22&height=180
> >>>>>
> <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>
> >>>>
> <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>>
> >>>>> .org%2Cguillaume%2Ccatch22&height=180>
> >>>>>> 2016-08-29 12:23 GMT+02:00 Guillaume Sueur
> >>>>> <no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>
> <mailto:no-reply at neogeo-online.net <mailto:no-reply at neogeo-online.net>>
> >>>>> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>>
> >>>> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>
> >>>> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>>>
> >>>>>> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>
> >>>> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>>
> >>>>> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>
> >>>> <mailto:no-reply at neogeo-online.net
> <mailto:no-reply at neogeo-online.net>>>>>:
> >>>>>>
> >>>>>> Hi list,
> >>>>>>
> >>>>>> I am experiencing a weird problem with geonode and
> >>>> geoserver
> >>>>> rest API.
> >>>>>> Here is the story. I have a bunch of layers in
> >>>> Geoserver, and
> >>>>> I can
> >>>>>> updatelayers from Geonode without any problem, having the
> >>>>> thumbnails
> >>>>>> correctly created in uploaded/thumbs directory, and
> >>>> correctly
> >>>>> set to
> >>>>>> www-data ownership afterwards to avoid any problem when
> >>>>> updating from
> >>>>>> the web interface.
> >>>>>>
> >>>>>> Then, if I use the "Define Thumbnail" button from the
> >>>> Layer
> >>>>> Edit Window,
> >>>>>> an empty image is created over the previously created
> >>>>> thumbnail. I dig a
> >>>>>> bit into the code trying to locate the issue. It seems it
> >>>>> comes from
> >>>>>> geoserver api which replies to the request emitted in
> >>>>>> geoserver/helpers.py on line 1687 with :
> >>>>>>
> >>>>>> Thumbnail created : {'date': 'Mon, 29 Aug 2016
> >>>> 10:19:56 GMT',
> >>>>> 'status':
> >>>>>> '405', 'content-length': '0'
> >>>>>> , 'allow': 'GET', 'server':
> >>>> 'Noelios-Restlet-Engine/1.0..8'}
> >>>>>>
> >>>>>> which means that the Method Not allowed error wasn't
> >>>> caught back
> >>>>>> correctly by geonode who continued the process and
> >>>> wrote the empty
> >>>>>> content to a new file.
> >>>>>>
> >>>>>> I just don't understand why I received this 405 HTTP
> >>>> error in this
> >>>>>> situation, that I have seen working well on other Geonode
> >>>>> Instances.
> >>>>>>
> >>>>>> I've made the installation following the custom
> >>>> installation
> >>>>> guide last
> >>>>>> week, so I guess with some fresh github code.
> >>>>>>
> >>>>>> Any clue ?
> >>>>>>
> >>>>>> Best regards
> >>>>>>
> >>>>>> Guillaume
> >>>>>> _______________________________________________
> >>>>>> geonode-devel mailing list
> >>>>>> geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>
> >>>>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>>
> >>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>>
> >>>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>
> >>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>>>
> >>>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>
> >>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>>
> >>>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>
> >>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>>>>
> >>>>>> http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>
> >>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>>
> >>>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>
> >>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>>>
> >>>>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>
> >>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>>
> >>>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>
> >>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Simone
> >>>>> _______________________________________________
> >>>>> geonode-devel mailing list
> >>>>> geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>
> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>>
> >>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>>
> >>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>
> >>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>>>
> >>>>> http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>
> >>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>>
> >>>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>
> >>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Simone
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Simone
> >>>> _______________________________________________
> >>>> geonode-devel mailing list
> >>>> geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>
> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>>
> >>>> <mailto:geonode-devel at lists.osgeo.org
> <mailto:geonode-devel at lists.osgeo.org>>
> >>>> http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>
> >>>
> >
> _______________________________________________
> geonode-devel mailing list
> geonode-devel at lists.osgeo.org <mailto:geonode-devel at lists.osgeo.org>
> http://lists.osgeo.org/mailman/listinfo/geonode-devel
> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>
>
>
More information about the geonode-devel
mailing list