WebSockets interception (break point) cannot be disabled

[GoogleCodeExporter]

What steps will reproduce the problem?

0. Run ZAP.
1. Launch Firefox, point it to ZAP.
2. Visit http://www.websocket.org/echo.html.
3. From the demo page, clink “Connect” to establish a WebSocket connection.
4. Send a WebSocket (WS) message.
5. The WS messages appear in ZAP WebSockets tab but are not intercepted by 
default.
6. Click in the “X” inside the ZAP WebSockets tab to set a break point for 
WebSockets. Confirm the popup.
7. Send a WS message.
8. Now, WS messages are intercepted by ZAP in the “Break” tab.
9. In order to stop WS interception, go to ZAP Break Points tab and uncheck the 
WebSockets entry (Enabled: off).
10. Send a WS message.
11. The WS message is still intercepted, although the associated breakpoint is 
disabled.
12. In order to REALLY try to stop WS interception, go to ZAP Break Points tab, 
right click in the WebSockets entry and select “Remove”.
13. Send a WS message.
14. The WS message is still intercepted.

What is the expected output? What do you see instead?

It seems WebSockets interception (break points) cannot be disabled. I expect 
both disabling the WS break point or removing the break point will turn off WS 
interception.

What version of the product are you using? On what operating system?

ZAP 2.3.1,  OS X 10.10.x, Java 1.8.x.

Please provide any additional information below.

Original issue reported on code.google.com by raul.si...@gmail.com on 19 Mar 2015 at 12:26

[GoogleCodeExporter]

I can confirm this issue in Zap version 2.4, OSX 10.9.5 and Java 1.7. The only 
way to turn off a custom breakpoint is to close Zap and re-open it. +1!

Original comment by aaron.sn...@gmail.com on 2 Jun 2015 at 10:20

[GoogleCodeExporter]

ZAP has been migrated to github

This issue will be on github issues with the same ID: 
https://github.com/zaproxy/zaproxy/issues

Original comment by psii...@gmail.com on 5 Jun 2015 at 9:18

• Changed state: Done