On 01/03/19 20:09, Sven Meier wrote:
Hi,
you're using a CsrfPreventionRequestCycleListener that prevents
WebSocket pushs to the client because there's no referrer set.
You should use a WebSocketAwareCsrfPreventionRequestCycleListener
instead.
Have fun
Sven
Hi Sven,
Your solution works
Hi,
you're using a CsrfPreventionRequestCycleListener that prevents
WebSocket pushs to the client because there's no referrer set.
You should use a WebSocketAwareCsrfPreventionRequestCycleListener instead.
Have fun
Sven
BTW credentials are admin/passwordd
Am 28.02.19 um 16:27 schrieb
On Thu, Feb 28, 2019 at 5:28 PM Matteo Alessandroni
wrote:
>
>
> On 28/02/19 15:11, Martin Grigorov wrote:
> > Hi,
> >
> > I've explained you earlier where to look at.
> > WebSocketRequestHandler#respond() is not called for some reason.
> > It is scheduled in AbstractWebSocketProcessor with
> >
On 28/02/19 15:11, Martin Grigorov wrote:
Hi,
I've explained you earlier where to look at.
WebSocketRequestHandler#respond() is not called for some reason.
It is scheduled in AbstractWebSocketProcessor with
requestCycle#scheduleAfterCurrent() but it seems later another
IRequestHandler is
Hi,
I've explained you earlier where to look at.
WebSocketRequestHandler#respond() is not called for some reason.
It is scheduled in AbstractWebSocketProcessor with
requestCycle#scheduleAfterCurrent() but it seems later another
IRequestHandler is scheduled and replaced it.
If you can reproduce
On 22/02/19 12:55, Matteo Alessandroni wrote:
On 22/02/19 12:46, Martin Grigorov wrote:
On Fri, Feb 22, 2019 at 1:40 PM Matteo Alessandroni
wrote:
On 22/02/19 12:28, Matteo Alessandroni wrote:
On 22/02/19 10:31, Martin Grigorov wrote:
On Fri, Feb 22, 2019 at 10:50 AM Matteo
On 22/02/19 12:46, Martin Grigorov wrote:
On Fri, Feb 22, 2019 at 1:40 PM Matteo Alessandroni
wrote:
On 22/02/19 12:28, Matteo Alessandroni wrote:
On 22/02/19 10:31, Martin Grigorov wrote:
On Fri, Feb 22, 2019 at 10:50 AM Matteo Alessandroni
wrote:
On 21/02/19 18:50, Martin Grigorov
On Fri, Feb 22, 2019 at 1:40 PM Matteo Alessandroni
wrote:
>
>
> On 22/02/19 12:28, Matteo Alessandroni wrote:
> >
> >
> > On 22/02/19 10:31, Martin Grigorov wrote:
> >> On Fri, Feb 22, 2019 at 10:50 AM Matteo Alessandroni
> >>
> >> wrote:
> >>
> >>>
> >>> On 21/02/19 18:50, Martin Grigorov
On 22/02/19 12:28, Matteo Alessandroni wrote:
On 22/02/19 10:31, Martin Grigorov wrote:
On Fri, Feb 22, 2019 at 10:50 AM Matteo Alessandroni
wrote:
On 21/02/19 18:50, Martin Grigorov wrote:
On Thu, Feb 21, 2019, 18:29 Matteo Alessandroni
wrote:
On 21/02/19 16:43, Martin Grigorov
On 22/02/19 10:31, Martin Grigorov wrote:
On Fri, Feb 22, 2019 at 10:50 AM Matteo Alessandroni
wrote:
On 21/02/19 18:50, Martin Grigorov wrote:
On Thu, Feb 21, 2019, 18:29 Matteo Alessandroni
wrote:
On 21/02/19 16:43, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 5:35 PM Matteo
On Fri, Feb 22, 2019 at 10:50 AM Matteo Alessandroni
wrote:
>
>
> On 21/02/19 18:50, Martin Grigorov wrote:
> > On Thu, Feb 21, 2019, 18:29 Matteo Alessandroni
> > wrote:
> >
> >>
> >> On 21/02/19 16:43, Martin Grigorov wrote:
> >>> On Thu, Feb 21, 2019 at 5:35 PM Matteo Alessandroni <
> >>
On 21/02/19 18:50, Martin Grigorov wrote:
On Thu, Feb 21, 2019, 18:29 Matteo Alessandroni
wrote:
On 21/02/19 16:43, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 5:35 PM Matteo Alessandroni <
skylar...@apache.org>
wrote:
On 21/02/19 16:30, Martin Grigorov wrote:
On Thu, Feb 21, 2019
On Thu, Feb 21, 2019, 18:29 Matteo Alessandroni
wrote:
>
>
> On 21/02/19 16:43, Martin Grigorov wrote:
> > On Thu, Feb 21, 2019 at 5:35 PM Matteo Alessandroni <
> skylar...@apache.org>
> > wrote:
> >
> >>
> >> On 21/02/19 16:30, Martin Grigorov wrote:
> >>> On Thu, Feb 21, 2019 at 5:24 PM Matteo
On 21/02/19 16:43, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 5:35 PM Matteo Alessandroni
wrote:
On 21/02/19 16:30, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 5:24 PM Matteo Alessandroni <
skylar...@apache.org>
wrote:
On 21/02/19 16:07, Martin Grigorov wrote:
On Thu, Feb 21,
On Thu, Feb 21, 2019 at 5:35 PM Matteo Alessandroni
wrote:
>
>
> On 21/02/19 16:30, Martin Grigorov wrote:
> > On Thu, Feb 21, 2019 at 5:24 PM Matteo Alessandroni <
> skylar...@apache.org>
> > wrote:
> >
> >> On 21/02/19 16:07, Martin Grigorov wrote:
> >>> On Thu, Feb 21, 2019 at 4:41 PM Matteo
On 21/02/19 16:30, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 5:24 PM Matteo Alessandroni
wrote:
On 21/02/19 16:07, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 4:41 PM Matteo Alessandroni <
skylar...@apache.org>
wrote:
On 21/02/19 12:14, Martin Grigorov wrote:
On Thu, Feb 21,
On Thu, Feb 21, 2019 at 5:24 PM Matteo Alessandroni
wrote:
> On 21/02/19 16:07, Martin Grigorov wrote:
> > On Thu, Feb 21, 2019 at 4:41 PM Matteo Alessandroni <
> skylar...@apache.org>
> > wrote:
> >
> >> On 21/02/19 12:14, Martin Grigorov wrote:
> >>> On Thu, Feb 21, 2019 at 12:11 PM Matteo
On 21/02/19 16:07, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 4:41 PM Matteo Alessandroni
wrote:
On 21/02/19 12:14, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 12:11 PM Matteo Alessandroni <
matteo.alessandr...@tirasa.net> wrote:
Hi,
On 21/02/19 11:05, Martin Grigorov wrote:
When
On Thu, Feb 21, 2019 at 4:41 PM Matteo Alessandroni
wrote:
> On 21/02/19 12:14, Martin Grigorov wrote:
> > On Thu, Feb 21, 2019 at 12:11 PM Matteo Alessandroni <
> > matteo.alessandr...@tirasa.net> wrote:
> >
> >> Hi,
> >>
> >> On 21/02/19 11:05, Martin Grigorov wrote:
> >>> When the WebSocket
On 21/02/19 12:14, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 12:11 PM Matteo Alessandroni <
matteo.alessandr...@tirasa.net> wrote:
Hi,
On 21/02/19 11:05, Martin Grigorov wrote:
When the WebSocket connection is established (maybe when the page is
loaded) you should see an entry in the
On Thu, Feb 21, 2019 at 12:11 PM Matteo Alessandroni <
matteo.alessandr...@tirasa.net> wrote:
> Hi,
>
> On 21/02/19 11:05, Martin Grigorov wrote:
> > When the WebSocket connection is established (maybe when the page is
> > loaded) you should see an entry in the Network tab.
> > If you select this
Hi,
On 21/02/19 11:05, Martin Grigorov wrote:
When the WebSocket connection is established (maybe when the page is
loaded) you should see an entry in the Network tab.
If you select this entry then on the right-side you should see any WS
messages to/from the server.
Yes I know how about WS
On Thu, Feb 21, 2019 at 11:40 AM Matteo Alessandroni
wrote:
> Hi,
>
> thanks for the answer!
> There are no js errors and browser devtool does not show any WS request
> so I'm not sure it's passing the correct body.
>
When the WebSocket connection is established (maybe when the page is
loaded)
Hi,
thanks for the answer!
There are no js errors and browser devtool does not show any WS request
so I'm not sure it's passing the correct body.
Anyway, if I add:
resourceCreateEvent.getTarget().appendJavaScript(String.format("addEndpoint('%s',
'%s', '%s');",
Hi,
Check the browser's Dev Tools' console for any JavaScript errors.
If there are no errors then check in the DevTools Network tab whether the
WebSocket response frame contains the JS code in its body. It must be
inside XML element. If it is not there at all then it must be
something on the
25 matches
Mail list logo
