WinRM transport error after inactivity

[Lat3magnet1c]

Hi,

first of all nice work! I love the tabbed autocompletion, this makes it much easier!

While testing and comparing with the "original" ruby winrm i discovered that when pressing enter after some time of inactivity (maybe 10minutes), the shell exits with the following error message: WinRM transport error: Bad HTTP response returned from the server. Code: 400, Content: ''.
Is there maybe some kind of "keepalive" used in the ruby version?

Nevertheless all other functions worked perfectly fine in my test!

[adityatelange]

Thanks for reporting this, I am aware of this and working on a fix.

[adityatelange]

Debugging shows that when a shell is created on remote machine:

• after 1 min of ShellInactivity, State is set to Disconnected.
• after 2 min and 5 Sec of ShellInactivity we get 400.

• the WSManInstance is not terminated yet and is still active on remote machine
• IdleTimeOut is PT7200.000S which is 2 hours.

rsp             : http://schemas.microsoft.com/wbem/wsman/1/windows/shell
lang            : en-US
ShellId         : AD2927B1-F008-4B2D-A04D-4E055D7B939A
ResourceUri     : http://schemas.microsoft.com/powershell/Microsoft.PowerShell
Owner           : DESKTOP-EPV20O8\flare
ClientIP        : 192.168.51.1
ProcessId       : 8548
IdleTimeOut     : PT7200.000S
InputStreams    : stdin pr
OutputStreams   : stdout
MaxIdleTimeOut  : PT2147483.647S
Locale          : en-US
DataLocale      : en-US
CompressionMode : NoCompression
ProfileLoaded   : Yes
Encoding        : UTF8
BufferMode      : Block
State           : Disconnected
ShellRunTime    : P0DT0H8M23S
ShellInactivity : P0DT0H6M20S
MemoryUsed      : 58MB
ChildProcesses  : 0

[adityatelange]

related to jborean93/pypsrp#21

[Lat3magnet1c]

Hey, thanks for the quick changes, as far as i tested its working now and the client is not disconnecting anymore.

[adityatelange]

A permanent fix has been found on this, I'll be pushing it soon, following with reversal of keep alive code.