Project

General

Profile

Actions

Bug #3045

closed

Lighttpd not able to delete temporary chunk files if client closes itself before upload completed

Added by FM360 4 months ago. Updated 4 months ago.

Status:
Missing Feedback
Priority:
Normal
Category:
core
Target version:
ASK QUESTIONS IN Forums:
Yes

Description

Lighttpd Version : 1.4.55

Issue : Lighttpd is not able to delete temporary chunk files if client closes itself
before upload completed.

Detail Description:
I am doing large file upload test in lighttpd and I can see that it is creating temperory file for chunks in /var/tmp.
I have observed that while uploading large file from client(here browser) to device running lighttpd server, if client closed (may be due to network gone) in between file upload operation, lighttpd is not able to wipe out temporary files that it has created during receiving chunks.


Files

Lighttpd_Tempfile_issue.mp4 (4.69 MB) Lighttpd_Tempfile_issue.mp4 Issue Demonstration FM360, 2020-12-16 11:32
Actions #1

Updated by gstrauss 4 months ago

Please share basic information including what operating system and version you are using, as different operating systems may handle temporary files differently.

Have you tested to see if this problem is still present or has been fixed in lighttpd 1.4.56?

Actions #2

Updated by gstrauss 4 months ago

  • Status changed from New to Need Feedback

Unable to reproduce in lighttpd 1.4.56 on Fedora Linux on x86_64.

Actions #3

Updated by FM360 4 months ago

Our device is running on Linux 4.9.226 kernel (aarch64 Flexible Linux)

Actions #4

Updated by gstrauss 4 months ago

  • Status changed from Need Feedback to Missing Feedback

Unable to reproduce in lighttpd 1.4.55 on Fedora Linux on x86_64.

Please see How to get support and then try to present as much information as possible on how to reproduce your issue.

Please also verify whether or not this is still an issue for you with lighttpd 1.4.56.

Actions #5

Updated by gstrauss 4 months ago

Unable to reproduce in lighttpd 1.4.56 on ROCK64 running Armbian aarch64 with upload directory /var/tmp (default) on ext4 fs.

Actions #6

Updated by FM360 4 months ago

Hi

I have again tested with lighttpd version 1.4.56.
And I was able to reproduce the same.

Please file the attachment with issue demonstration video.

  • Discription:
  • Lighttpd version : 1.4.56
  • Linux Version : Linux 4.9.226 kernel (aarch64 Flexible Linux)

STEPS

1) Start uploading large file from client (i.e browse or postman)PC.
2) Check chunks are being created in upload directory (/var/tmp) of lighttpd server device.
3) Close client network connection before all chunks are received.
4) Again enable client network and check that the temporary chunk files are still present at server directory(/var/tmp).

- Now this temporary chunk files will stay forever.

Actions #7

Updated by gstrauss 4 months ago

This isn't tiktok. I'm not interested in seeing you move your mouse.

You haven't provided any new information that is useful, other than that you probably do not understand TCP and how temporary network interruptions do not necessarily cause connections to drop.

If you cleanly shut down the lighttpd server (not kill -9), do the files get cleaned up? Or if you wait for connection timeouts, do the files get cleaned up?

Actions

Also available in: Atom