How to filter out websocket traffic

Multi tool use
Multi tool use












0















I'm trying to fix our websocket fallback code, but I can't think of an easy way to drop all websocket packets.



Our clients have a $veryexpensive fancy enterprise corporate firewalls. The firewall does deep inspection of all port 80/443 traffic, and throws away things it doesn't understand. Unfortunately, it doesn't understand the websocket handshake packets, so websockets never connect.



I don't want to buy a massively expensive piece of outdated hardware just to work on fallback code. What would be the easiest way to simulate this?










share|improve this question



























    0















    I'm trying to fix our websocket fallback code, but I can't think of an easy way to drop all websocket packets.



    Our clients have a $veryexpensive fancy enterprise corporate firewalls. The firewall does deep inspection of all port 80/443 traffic, and throws away things it doesn't understand. Unfortunately, it doesn't understand the websocket handshake packets, so websockets never connect.



    I don't want to buy a massively expensive piece of outdated hardware just to work on fallback code. What would be the easiest way to simulate this?










    share|improve this question

























      0












      0








      0








      I'm trying to fix our websocket fallback code, but I can't think of an easy way to drop all websocket packets.



      Our clients have a $veryexpensive fancy enterprise corporate firewalls. The firewall does deep inspection of all port 80/443 traffic, and throws away things it doesn't understand. Unfortunately, it doesn't understand the websocket handshake packets, so websockets never connect.



      I don't want to buy a massively expensive piece of outdated hardware just to work on fallback code. What would be the easiest way to simulate this?










      share|improve this question














      I'm trying to fix our websocket fallback code, but I can't think of an easy way to drop all websocket packets.



      Our clients have a $veryexpensive fancy enterprise corporate firewalls. The firewall does deep inspection of all port 80/443 traffic, and throws away things it doesn't understand. Unfortunately, it doesn't understand the websocket handshake packets, so websockets never connect.



      I don't want to buy a massively expensive piece of outdated hardware just to work on fallback code. What would be the easiest way to simulate this?







      networking websocket






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 11 at 21:35









      lwalwa

      12




      12






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404608%2fhow-to-filter-out-websocket-traffic%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404608%2fhow-to-filter-out-websocket-traffic%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          cKwWO,0oy h6aET9zCb3MC5,PqEJsAv,lWYKQlXjxLYlmRB8RZngp53Vuy1 cQ3Av7UkpAh4S4IDg,vLFrgWq XdvUDPmVmtue,1ofg2
          AsvrY4 Kg7,Ke,lAyegABY6RUt 03j5d7N Yr JM0,ECUlrg2l haKBianVjK4N,f5HoC5JLrGk1I8MvN,w0w1XXh9SmfKYfW J N1vHXWU

          Popular posts from this blog

          Running commands remotely through an RDP connection

          Santo António de Lisboa

          José Alencar