[
https://issues.apache.org/jira/browse/OPENMEETINGS-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118011#comment-17118011
]
Noddy edited comment on OPENMEETINGS-2374 at 5/27/20, 6:51 PM:
---------------------------------------------------------------
In additional to this, for same session where room was frozen on loading
screen, If i hit url /#room/<room_id_which_i_have_received_in_SOAP_response>,
room again works normally. That means authentication or validation is working
properly (logs also passed same).
*Hope this helps you.*
and one minor scenario i faced that is, when i got stable room after hitting
'/#room/<room_id>' in same session. If i pressed EXIT button on UI (left side
top corner), it redirects me to localhost:5080/openmeetings.
was (Author: noddy09):
In additional to this, for same session where room is freezed on loading
screen, If i hit url /#room/<room_id> which i have received on SOAP call, it
again works nomally. That means authentication or validation is working
properly (logs also passed same).
Hope this helps you.
and one minor scenario i faced that is, when i got stable room after hitting
'/#room/<room_id>' in same session. If i pressed EXIT button on UI (left side
top corner), it redirects me to localhost:5080/openmeetings.
> An HTTP error response in websocket communication would not be processed by
> the browser.
> ----------------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-2374
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2374
> Project: Openmeetings
> Issue Type: Bug
> Components: Room, SOAP/REST API
> Affects Versions: 5.0.0-M4
> Environment: Ubuntu 20.04 | docker container
> Reporter: Noddy
> Assignee: Maxim Solodovnik
> Priority: Major
> Labels: SSL, websocket
> Attachments: wb.log
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I created room normally with web-ui, everything works fine.
> But when i created room & logged in user using SOAP 'services/RoomService'
> and provide room URL (which redirects on /hash?secure=<random-hash> as
> usual), room freezed on loading screen and OM5 threw exception.
> Log file is attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
