Websockets API support
I'm running into wss more as we see the shift towards single page, media rich applications. As such, I often find the need to implement custom deserialization of binary websockets messages. It would be helpful if I could write Burp extensions to view and modify wss traffic.
Any near-term plans for this?
This isn’t in our near-term roadmap, sorry. We do plan to add API support for WebSockets at some point, but can’t currently offer an ETA for the feature.
Also, I am curious why simple functionality like copying all websocket messages out of the websockets history is not included in Burp, which was, I guess, one of the first things that worked for the HTTP history.
Unfortunately there hasn’t been further progress. WebSockets pose some difficulty for us, as the whole of Burp is heavily based on the “request / response” model which fits HTTP well but doesn’t fit WebSockets.
You’re right, we could make some minor improvements, such as allowing copying. I guess small improvements like that have been on hold until we do the major work to support WebSockets properly.
I’ve linked your comment to the development story; repeated user requests do help justify allocating development resource.
Thanks for getting in touch.