hi!
I've been trying to setup restconfig plugin with geoserver (both 2.0.2
and 1.7.6, with respective plugin versions).
however, any request to the REST interface I make ends up with a 404
sent back by the noelios restlet engine:
< HTTP/1.1 404 Not Found
< Date: Tue, 03 Aug 2010 11:25:34 GMT
< Server: Apache-Coyote/1.1
< Via: 1.1 172.30.0.150
< Content-Length: 0
< Content-Type: application/xml
<
* Connection #0 to host 172.30.0.150 left intact
* Closing connection #0
I've searched the web far and wide, but can't seem to find a similar
problem. and yes, authentication is set up correctly. 
being at a complete loss about what is going on here, can someone,
please, give me a hint on what I should be looking at ...
attaching a full debug log of processing of a POST request to
rest/workspaces URL on 2.0.2.
regards,
jaKa
rest-post-log.txt (11.3 KB)
are you using tomcat or jetty? I've had problems with the rest plugin
when using tomcat which went away when using jetty.
We've had problems with other plugins based on tomcat versions less
than 6.0.28 so changing to an up to date tomcat may fix this (but I
haven't tried that yet).
Ian
--
Ian Turton
hi, Ian!
On Tue, 2010-08-03 at 10:40 -0400, Ian Turton wrote:
are you using tomcat or jetty? I've had problems with the rest plugin
when using tomcat which went away when using jetty.
We've had problems with other plugins based on tomcat versions less
than 6.0.28 so changing to an up to date tomcat may fix this (but I
haven't tried that yet).
it was indeed a problem caused by tomcat. by tomcat configuration, to be
precise. (occurs also on latest 6.0.29)
I run tomcat behind a frontend apache2 that proxies inbound connections
to port 80 on public interface to tomcat listening only on localhost and
on port 20002. thus I have a Connector with proxyName and proxyPort
attributes set in the tomcat's server.xml.
removing proxyName and proxyPort fixes the problem. unfortunately, this
might prove a problem for other web applications I run in the same
servlet container.
not sure what exactly is the reason that proxy settings confuse the
restlet machinery, but I am reluctant to blame tomcat for this ... more
likely it is some obscure bug in the restlet code.
regards,
jaKa
On Tue, Aug 3, 2010 at 11:01 AM, Jaka Močnik <jaka@anonymised.com> wrote:
hi, Ian!
On Tue, 2010-08-03 at 10:40 -0400, Ian Turton wrote:
are you using tomcat or jetty? I've had problems with the rest plugin
when using tomcat which went away when using jetty.
We've had problems with other plugins based on tomcat versions less
than 6.0.28 so changing to an up to date tomcat may fix this (but I
haven't tried that yet).
it was indeed a problem caused by tomcat. by tomcat configuration, to be
precise. (occurs also on latest 6.0.29)
I run tomcat behind a frontend apache2 that proxies inbound connections
to port 80 on public interface to tomcat listening only on localhost and
on port 20002. thus I have a Connector with proxyName and proxyPort
attributes set in the tomcat's server.xml.
removing proxyName and proxyPort fixes the problem. unfortunately, this
might prove a problem for other web applications I run in the same
servlet container.
not sure what exactly is the reason that proxy settings confuse the
restlet machinery, but I am reluctant to blame tomcat for this ... more
likely it is some obscure bug in the restlet code.
That is interesting as that's pretty much the set up I'm running -
when I get some time I'll look at it some more.
You should probably file a JIRA describing the problem and fix so this
doesn't get forgotten.
Ian
--
Ian Turton