Progress® Telerik® Fiddler™ Classic Feedback Portal
Back to Feed
Request a Feature Report a Bug
Unplanned
Last Updated: 07 Apr 2025 06:19 by ADMIN
Eiji
Created on: 03 Apr 2025 07:50
Type: Bug Report
0
The URL displayed in the WebSocket capture is incorrect.

I am using the following version

Progress Telerik Fiddler Classic v5.0.20253.3311 for .NET 4.6.2

When capturing WebSocket communication with a URL of "ws://10.133.37.150:9999/", the request line in the Inspectors' Headers view is correct as follows:
"GET ws://10.133.37.150:9999/ HTTP/1.1"

However, the URL column in the left pane says "ws://10.133.37.150:9999/", but the correct value is "/".

Also, the Inspectors' Raw tab says
"GET http://10.133.37.150:9999ws://10.133.37.150:9999/ HTTP/1.1", but the correct value is
"GET ws://10.133.37.150:9999/ HTTP/1.1".

I think this is a bug

 

Attached Files:
2 comments
Eiji
Posted on: 04 Apr 2025 01:12

Sorry. I mistakenly thought that I couldn't attach files other than images.

The following environments have been tested.
The WebSocket server and client are running on the same host.

  • Windows 11 Pro
  • wscat 6.0.1
  • AzulJDK 21.0.6
  • sbt 1.10.10

The procedure for testing is as follows.

  1. Start the WebSocket server with the following command:

    wscat -l 9999
  2. Clone the main branch of the gatling-sbt-pluguin-demo repository.

    https://github.com/gatling/gatling-sbt-plugin-demo
  3. Modify XXX.XXX.XXX.XXX in the WSSample1.scala file to the IP address of the server environment.
  4. Place WSSample1.scala under the cloned gatling-sbt-plugin-demo/src/test/scala.(WSSample1.scala is included in the attached file WSSample1.zip.)
  5. Start Fiddler.
  6. Run Gatling (WebSocket client) using the following command in the gatling-sbt-plugin-demo folder.
    sbt "Gatling/testOnly sim.WSSample1"


I tried it with other clients, and it seems to occur when the request line of the WebSocket opening handshake contains an absolute URI.



Attached Files:
ADMIN
Nick Iliev
Posted on: 03 Apr 2025 09:23

Hi Eiji,

 

Is the above happening only with a specific WebSocket endpoint ? We tried to reproduce the issue, but so far, to no avail.

Let us know if you have a public WS APi endpoint that we can use to reproduce the issue so that we can investigate the matter further. This is also valid for a ticket with ID 1383759 (https://feedback.telerik.com/fiddler/1683759-websocket-messages-may-appear-as-part-of-the-websocket-opening-handshake) . Sharing steps to reproduce and a demo app or API endpoint will be of great advantage.

As a side note, you could also retest your scenario with Fiddler Everywhere, where the team has implemented more advanced techniques for capturing WebSocket traffic - for the sake of noting if the issue is strictly related to FIddler Classic or the specific applicaiton/endpoint.

 

Regards,
Nick Iliev
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Create an account Log In
View
Type
Status