Docker: Internal server error about imapsync

[gilleslamiral]

The Docker online imapsync service is new. I haven't used it in production. It doesn't use the Apache server but a Perl module named Net::Server::HTTP
I was asking myself recently about the default timeout value of it. Well, I have an answer from you now.
I'll update the image with a better value than the default 60 seconds. 3600 should fix the issue.
https://metacpan.org/pod/Net::Server::HTTP :
...
timeout_header
Defaults to 15 - number of seconds to wait for parsing headers.
timeout_idle
Defaults to 60 - the number of seconds a request can be idle before the request is closed.

[xyzulu]

That makes sense.. thanks!

[gilleslamiral]

Update made, have a go

 docker pull gilleslamiral/imapsync

[xyzulu]

That has fixed the 500 error for sure.. I saw a process run for over 4 mins this time. Still, the docker implementation of https://imapsync.lamiral.info/X/ in my case doesn't give the usual 6s feedback. Yet, if I run the same sync with the same container on the same hardware via the cli.. I get plenty of feedback (visual progress).

It's not my specialty, but perhaps another web server ie nginx might be better in the container?? I think the web server part here is not optimal.

Edit: there is also Caddy

[gilleslamiral]

With the Net::Server::HTTP server, the running feedback interval is not based on time, it is every 4 Kb of output. It's not my decision, I discovered it as you did. Anyway, the imap job is done, so that's not a first bug issue for me, even I did spend hours on it, just to understand where it comes from. I'll post a feature request to Net::Server::HTTP maintainers.

For Ngnix, I just know its name so not for now.
It could be Apache, I know it quite well, but I still have to learn, play and master the Docker way of it.

Caddy? I just learned the name...

[xyzulu]

I did a big sync today.. so far so good.. thanks for your work on this docker version..