tomcat
On Jan 18, 2011, at 2:49 PM, Igor Vaynberg wrote:
not sure then. seems rather strange that you cant reproduce it
locally. what container is it running in?
-igor
On Tue, Jan 18, 2011 at 12:41 PM, Douglas Ferguson
doug...@douglasferguson.us wrote:
There is no proxy
On Jan 18,
well, dont know what to tell you. seems really strange to me.
-igor
On Wed, Jan 19, 2011 at 5:08 PM, Douglas Ferguson
doug...@douglasferguson.us wrote:
tomcat
On Jan 18, 2011, at 2:49 PM, Igor Vaynberg wrote:
not sure then. seems rather strange that you cant reproduce it
locally. what
I only see it in production
On Jan 17, 2011, at 6:38 PM, Igor Vaynberg wrote:
not really sure what is happenning. that url is pretty badly mangled.
can you set a breakpoint in part of the code that generates it and see
if its wicket or someone is playing with the url.
-igor
On
is the app proxied? could be a proxy mangling it on a rewrite.
-igor
On Tue, Jan 18, 2011 at 1:57 AM, Douglas Ferguson
doug...@douglasferguson.us wrote:
I only see it in production
On Jan 17, 2011, at 6:38 PM, Igor Vaynberg wrote:
not really sure what is happenning. that url is pretty
There is no proxy
On Jan 18, 2011, at 10:48 AM, Igor Vaynberg wrote:
is the app proxied? could be a proxy mangling it on a rewrite.
-igor
On Tue, Jan 18, 2011 at 1:57 AM, Douglas Ferguson
doug...@douglasferguson.us wrote:
I only see it in production
On Jan 17, 2011, at 6:38 PM,
not sure then. seems rather strange that you cant reproduce it
locally. what container is it running in?
-igor
On Tue, Jan 18, 2011 at 12:41 PM, Douglas Ferguson
doug...@douglasferguson.us wrote:
There is no proxy
On Jan 18, 2011, at 10:48 AM, Igor Vaynberg wrote:
is the app proxied? could
Thoughts?
On Jan 14, 2011, at 5:44 PM, Douglas Ferguson wrote:
This looks like it must have been one of them.
- - [13/Jan/2011:14:26:34 -0600] GET
/?wicket:interface=:26::INewBrowserWindowListener:: HTTP/1.1 302 -
not really sure what is happenning. that url is pretty badly mangled.
can you set a breakpoint in part of the code that generates it and see
if its wicket or someone is playing with the url.
-igor
On Mon, Jan 17, 2011 at 11:56 AM, Douglas Ferguson
doug...@douglasferguson.us wrote:
Thoughts?
Sorry about my previous title.
I'm not sure what's causing this, but I've spoken with some of my clients, who
spawned these errors and they weren't manipulating the querystrings..
So I'm not sure how two pagemap paramenters are getting in there..
D/
On Jan 13, 2011, at 11:40 AM, Douglas
do their apache logs contain a sample of the url that caused this
error? would be helpful to see one.
-igor
On Fri, Jan 14, 2011 at 3:12 PM, Douglas Ferguson
doug...@douglasferguson.us wrote:
Sorry about my previous title.
I'm not sure what's causing this, but I've spoken with some of my
This looks like it must have been one of them.
- - [13/Jan/2011:14:26:34 -0600] GET
/?wicket:interface=:26::INewBrowserWindowListener:: HTTP/1.1 302 -
11 matches
Mail list logo
