Re: [Geoserver-users] GeoServer to GeoWebCache comm over port 80

[Arne K. <ar...@ti...>]

  Yes, 2.0.1 internalizes the communication, so it happens in Java 
without network access.

However, to me it seems like you should just allow HTTP communication on 
127.0.0.1, and not on the public interface. Anyone that can sniff 
packets on the loopback interface already has superuser privileges on 
the machine, so I don't think you gain anything for your troubles.

I don't think patching such an old version to support SSL is worth it.
-Arne



On 9/30/10 1:12 PM, Ottofaro, Jack wrote:
>
> We're running an older version of GeoServer , version 1.7.1 I believe, 
> and it appears to communicate internally with the GeoWebCache plug-in 
> over port 80. On our production system port 80 is unavailable -- only 
> comm. over secured ports is allowed, e.g. port 443. I read a post on 
> the internet that said as of GeoServer version 2.0.1 it no longer uses 
> http to communicate to GeoWebCache since it's in the same JVM. Is this 
> true? More importantly, will I not have the port 80 issue with the 
> GeoServer to GeoWebCache comm.? If not, is there a way to get it to 
> communicate to GeoWebCache over port 443 and https?
>
> Thanks,
>
> Jack Ottofaro
>
> UL/UC2 Software Lead
>
> Phone: (757) 896-4877
>
> Lockheed Martin IS&GS
>
> 22 Enterprise Parkway, Suite 120
>
> Hampton, VA 23666
>
> Fax: (757) 896-4891
>
> E-mail: jac...@lm... <mailto:jac...@lm...>
>
>