move this getClientInfo() call into the page, which
forces the javascript page to render prior to the page and not in the ajax
call.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Ajax-response-render-as-source-in-the-browser-tp3028722p4385693.html
Sent from the Users forum ma
just to say we still have this issue and its getting more and more
worse as people are moving to FF and Chrome.
We have no idea how to solve as we cannot reproduce it consistently.
On Mon, Dec 13, 2010 at 8:41 PM, Wayne W wrote:
> Hello everyone,
>
> I thought you might be interested. At the week
Hello everyone,
I thought you might be interested. At the weekend I experienced this
problem myself on my local machine, so I had the chance to debug and
figure what was happening.
The short version is 99.9% sure its a javascript engine bug on Firefox
(and we've had a couple of users say they had
Hello,
we've upgraded the apache to 2.2.15 in production and this made no difference.
However today we got a screen shot from one client who has been having
the issue see:
https://home.glasscubes.com/share/code/8a8c7ecf37fe9d95cefaf787529b0828
(you'll need to download to see the details of the UR
We're running 2.2.15 with the AJP connector. Before we'd pinpointed
our problem, we were considering using the HTTP connector instead.
That affects the requestor's IP in Tomcat though, so I'm glad we
didn't have to.
On Fri, Nov 12, 2010 at 12:31 AM, Wayne W wrote:
> Thanks Dan,
>
> I thought I'd
Thanks Dan,
I thought I'd foudn my answer then! However we're using:
Server version: Apache/2.2.9 (Unix)
Server built: Dec 10 2008 18:22:18
So it looks like we already have that fix.
Which version are you running?
On Fri, Nov 12, 2010 at 5:19 AM, Dan Retzlaff wrote:
> We had this issue wi
We had this issue with Apache HTTPD in front of Tomcat. "Random" pages
would be rendered as text/plain instead of text/html.
Bug: https://issues.apache.org/bugzilla/show_bug.cgi?id=43478
Discussion:
http://markmail.org/message/btwcnbl2i7ftwj4n#query:mod_proxy_ajp%20plain+page:1+mid:btwcnbl2i7ftwj
well, you do have apache infront of tomcats, which *is* a proxy. i
would write a jmeter script that tried to reproduce this and when you
can run it against tomcat (not going through apache) and see if you
can repro it that way. im guessing its something in your apache config
since you are the only
> the browser. do you have a proxy between the servlet container and the
> outside? maybe something is injecting a redirect or something weird.
I did wonder if there was weird redirect issue, but after doing a lot
of reading yesterday it seems the xmlrequest object *should* handle
redirects fine.
the only way i can see that happenning if the url is no longer
processed by wicket's ajax support and so the response just ends up in
the browser. do you have a proxy between the servlet container and the
outside? maybe something is injecting a redirect or something weird.
-igor
On Sun, Nov 7, 20
thanks Igor,
I've just spent a few hours stepping though the code and I cannot see
anyway the content type could be set wrong - I see the content type is
set in the final respond(requestCycle) method, so I'm now thinking
this is not a content type issue.
However we just got another user email wit
see AjaxRequestTarget class, this is where the response is generated
on the serverside
wicket-ajax.js is where it is processed on the client side.
-igor
On Sat, Nov 6, 2010 at 2:49 AM, Wayne W wrote:
> Hi Igor,
>
> Whats odd is that one guy was getting it on his iPad consistently and
> when we
Hi Igor,
Whats odd is that one guy was getting it on his iPad consistently and
when we asked him to try his desktop he's got the same problem on
Firefox on Mac. We initially though it might have been a browser
issue. We then got another user who got it only once on Chrome on
windows - all in the s
it may be a content type issue, but it is still weird because the
response is received by the xml http request object, not the browser
directly. strange indeed.
-igor
On Fri, Nov 5, 2010 at 7:51 AM, Wayne W wrote:
> Hi,
>
> has anyone had this issue? We're getting emails from our users that
> so
Hi,
has anyone had this issue? We're getting emails from our users that
sometime when clicking on an ajax link the raw wicket ajax response is
being rendered on the browser - ie the just see all the html source
code on the page. Its not any particular page.
Anyone seen this or has any ideas?
Th
15 matches
Mail list logo
