Lonko's questions

I have a long poll clients that connect to nginx and upstream to kestrel dot net. Clients have keepalive set that after 2 minutes connection breaks. On nginx side i have listen 0.0.0.0:xxx ssl so_keepalive=5m:10:5; So roughly 6 minutes

I pull the eth cable out of the cable, preventing any transfers and client detects a connection break, but my upstream server does not. Upstream server never detects this.

Now is the nginx not detecting this break ? and then not closing connection to upstream ? Or what am i doing wrong?

Thank you

I have set the following configuration:

 location /upl {
       root /storage/www/upl/data;
       client_body_temp_path   /storage/www/upl/client_tmp;

       dav_methods  PUT DELETE MKCOL COPY MOVE;

       create_full_put_path   on;
       dav_access             group:rw  all:r;
  }

I upload a file with: curl -T test.txt http://x.xx.xx.xx:8080/upl

All of my files end up in data folder but all files have the same name "upl" the same as the location ?! Why :S

Please help

BR,

Normally when you pull the network cable out of a network device (which simulates some drop on the network, so an obscure disconnect), the underlaying sockets do not detect a disconnect (at least our units don't) so we use keep alive to drop connection and reconnect.

All units use hourly long poll to nginx server. So my question is:

If the unit does not detect a cable disconnect (and probably 100 other situations on the network), then also nginx does not disconnect the socket and that socket stays open?

Stay open for how long?

Should we use on the nginx side also tcp keep alive towards client? How?

we have a strange problem on older linux kernel embedded devices that still uses /etc/tz and $TZ for setting the timezone and dst

Our TZ variable has value: 'MET-1MEDT,M3.5.0,M10.5.0/03:00

And yesterday the time did not go BACK as it should. Was this somekind of bug in DATE on older linux releases ? How to remedy this fast?

Or what?

Thank you!