[ https://issues.apache.org/jira/browse/MYFACES-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944452#comment-17944452 ]
Werner Punz edited comment on MYFACES-4720 at 4/14/25 8:15 PM: --------------------------------------------------------------- Yes looks like it, not sure what the fix is but probably we just have to add a similar code as is for https -> wss! I have to admit the websocket part is the weakest part regarding my knowledge, it was not written by me, I basically just ported the old code over with some cleanup to the new codebase! So everything I say should be taken with a grain of salt here! was (Author: werpu): Yes looks like it, not sure what the fix is but probably we just have to add a similar code as is for https -> wss! > WebSocket secure protocol > ------------------------- > > Key: MYFACES-4720 > URL: https://issues.apache.org/jira/browse/MYFACES-4720 > Project: MyFaces Core > Issue Type: Bug > Components: General > Affects Versions: 4.0.3, 4.1.1 > Reporter: Melloware > Assignee: Werner Punz > Priority: Major > > [~werpu] this was reported at Mojarra: > https://github.com/eclipse-ee4j/mojarra/issues/5578 > I believe MyFaces has the same issue in PushImpl.ts found here > {code:javascript} > export module PushImpl { > const URL_PROTOCOL = DQ.global().location.protocol.replace("http", "ws") > + "//"; > {code} > What are your thoughts? -- This message was sent by Atlassian Jira (v8.20.10#820010)