I am using a win service that is sending a POST request to some host. I'm able to filter/catch it in Wireshark and there is a response there, but nothing about request and its headers. Could you someone show me the right way, please :) Screenshot is below Thank you.
I'm using v.2.6.1. Windows 10 x64
Your capture contains only traffic from the Server to the Client. The reason may be due to the way you obtained your capture. If you did a port span, you may have only spanned the Tx of the server switch port and not both Tx and Rx.
Can you provide any information on how you are capturing your data?
Sure.
"Start Wireshark.exe" on what? The server itself, or are you capturing from another machine? If from another machine, how are you capturing the data to/from the server? Port Span, TAP, L1 Hub, etc?
Hm.. I am starting it on my local notebook. With default settings just choosing the interface (Ethernet #..) from the list. Start catching traffic and the filter it with display filter.
I believe there is no port span or tap. Not sure what is L1 Hub.
Just to make an analogy with Fiddler - you start the app, do your http things in the browser and see all the requests/responses there. My expectations were the same using wireshark :)
I think I found the answer... I uninstalled 2.6.1 version and installed - Old Stable Release (2.4.7) With 2.4.7 everything works and I see the requests (POST/GET/etc)
Bug in 2.6.1?
Thanks!
Asked: 2018-06-06 10:08:49 +0000
Seen: 6,151 times
Last updated: Jun 12 '18
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
do you see the request if you Follow the tcp stream?
No. Under "Entire Conversation" dropdown list it states that no request was sent to target destination (0 bytes) Only response is available.
Screenshot - https://ibb.co/fJaBL8
Could you make the entire capture available on some site, so we can download it and look at it?
If not, could you show us the summaries of packets 1 through 59?
Try this link - https://ufile.io/71mrj Is this what you need? There are packets from #53 to #62 only related to the destination IP.