Can't connect to websocket with authorization header about stompclientlib

[iOSDias]

@cedb777 @cleverClosure
I also can not to send headers through connectionHeaders, but I send it in request, like this

    var socketRequest: NSURLRequest {
        let webSocket = URL(string: urlString)!
        var request = URLRequest(url: webSocket)
            request.setValue(("Bearer " + token).toBase64, forHTTPHeaderField: "Authorization")
        return request as NSURLRequest
    }

[cleverClosure]

It worked for me with this code:
` let url = URL(string: "wss://(defaultSocketBase)/push?access_token=(token)")!

    let request = NSURLRequest(url: url)

    let headers: [String: String] = ["heart-beat": "20,20"]

    socketClient.openSocketWithURLRequest(request: request, delegate: self, connectionHeaders: headers)`

[jbarros35]

@cedb777 @cleverClosure
I also can not to send headers through connectionHeaders, but I send it in request, like this

    var socketRequest: NSURLRequest {
        let webSocket = URL(string: urlString)!
        var request = URLRequest(url: webSocket)
            request.setValue(("Bearer " + token).toBase64, forHTTPHeaderField: "Authorization")
        return request as NSURLRequest
    }

For the ones who could not make it using headers on connection, try this, that approach works on my environment.

[WrathChaos]

Hello @cleverClosure ,
I need an example to test it out. Can you provide it?

[cleverClosure]

Can I send it to you privately somehow? I don't want the url to be public

[WrathChaos]

You can send me an email : [email protected]

[cleverClosure]

I've sent you an email

[WrathChaos]

Hello again @cleverClosure,
As I mentioned on the mail, I got this error from your server:
didFailWithError: Optional(Error Domain=SRWebSocketErrorDomain Code=2133 "Invalid Sec-WebSocket-Accept response" UserInfo={NSLocalizedDescription=Invalid Sec-WebSocket-Accept response})

Can you provide a working authentication token or please check your server part :)

[cleverClosure]

Yes, that is exactly what I get when I use ws instead of wss or https. Here is the new token: 451ac7a5-ad93-4859-8c62-b41e96d6a34d

[cleverClosure]

The server side works, because I am able to connect to it from the web client

[WrathChaos]

@cleverClosure
Have you checked these issues?
#30 and #32 ?

[cleverClosure]

The webserver works on sockJS but adding /websocket to the url didn't help

[WrathChaos]

@cleverClosure I'm really sorry but I could not find the problem about your issue :(
I've tried another websocket with authentication and it works without any issue. I have only left is that your websocket backend might have an issue about it.

[cleverClosure]

Can I ask you which websocket with auth did you try (the one you were able to connect successfully)? Is that local webserver or something?

[WrathChaos]

I've tried on a very simple local webserver. Unfortunately, I do not have any other options.

[said13]

Someone solved this problem?
I have the same issue.

[cedb777]

Same issue! Someone solved this ?

[WrathChaos]

@said13 and @cedb777, Can you guys provide me with an example of the issue? Because I could not reproduce it on my own simple WebSocket server.

[said13]

@iOSDias Hi! It works?

[iOSDias]

@said13 yes

[WrathChaos]

Finally, I closed the issue :) Please open a new one if you still have a problem.