Avatar for Username

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊，或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

此討論串已被封存。 如果您有需要幫助，請新增一個新問題

Firefox doesn't send the TCP FIN flag when the server has been sent it.

  • 2 回覆
  • 1 有這個問題
  • 2 次檢視
  • 最近回覆由 iwo_andonow

iwo_andonow
iwo_andonow
more options

I have test web server that do redirect (304) when a button on a web page is clicked and tries to close the TCP socket with flags FIN and PSH. Firefox acknowledges the packet with no FIN flag set causing the server to re-transmit the message many times. I'm attaching Wireshark captured packets.

I have test web server that do redirect (304) when a button on a web page is clicked and tries to close the TCP socket with flags FIN and PSH. Firefox acknowledges the packet with no FIN flag set causing the server to re-transmit the message many times. I'm attaching Wireshark captured packets.

所有回覆 (2)

vinodh.g
vinodh.g
more options

Is the behavior different on other web browsers? I think 304 is not a redirect. It is 'not modified'. Try using Firefox menu 'tools' -> 'Web Developer' -> 'Network' , it may give some pointers.

iwo_andonow
iwo_andonow 提出問題者
more options

Thank you for your advice! I'll investigate what happens through the 'Web Developer' -> 'Network'. I was using 304 with another web page that is not in the browser cache to force the browser to open another socket and load the page. I saw that in some example and I'm not sure that it is the most correct way of doing that. I tried the same scenario with IE11and it looked much cleaner: server sends FIN+PSH, client sends ACK+FIN, server sends ACK and the socket gets closed. I think I need to dig into the problem more and to narrow it down before you spend time on this. Thanks once again for the advices! PS: I can't upload here Wireshark packets file anymore.