search

denandz / glorp

A CLI-based HTTP intercept and replay proxy
BSD 3-Clause "New" or "Revised" License
248 stars 14 forks source link

Error in create a new blank replay item #3

Closed webmastak closed 3 years ago

webmastak commented 3 years ago

If you send a request via curl, then everything works as it should. If in the tab Replay -> Ctrl + b then it gives an error.

2020/10/06 14:33:31 Logger started                                                                                                                     
2020/10/06 14:33:44 [+] ReplayView - AddItem - Adding replay item with ID: new                                                                         
2020/10/06 14:34:25 [+] Replay - SendRequest Host: example.com Port: 80 TLS:  false                                                                    
2020/10/06 14:34:26 [+] Replay - sendTCP - Sent: 120                                                                                                   
2020/10/06 14:34:56 [!] Replay sendTCP: read tcp 192.168.0.6:43484->93.184.216.34:80: i/o timeout

error

denandz commented 3 years ago

Your socket is timing out because the server is holding the connection open. You need a Connection: close header. This isn't an issue with creating new replays

denandz commented 3 years ago

Commit 0227061cd21bfbf6327641861ab85e25cc1ed209 has tweaked glorp to display any data available on a timed out socket

webmastak commented 3 years ago

Copied GLORP from master. Connection: close header didn't help, same error!

2020/10/07 14:39:04 [+] ReplayView - AddItem - Adding replay item with ID: new                                                               
2020/10/07 14:39:58 [+] Replay - SendRequest Host: example.com Port: 80 TLS:  false                                                          
2020/10/07 14:39:58 [+] Replay - sendTCP - Sent: 166                                                                                         
2020/10/07 14:40:28 [!] Replay sendTCP: read tcp 192.168.0.6:57420->93.184.216.34:80: i/o timeout
denandz commented 3 years ago

dont forget your CRLFs! glorp-replay

https://tools.ietf.org/html/rfc2616#section-5 might be helpful

webmastak commented 3 years ago

Does not work! 002

ifconfig:

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:02:a1:dc:73  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.6  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::3a2c:4aff:fee7:da99  prefixlen 64  scopeid 0x20<link>
        ether 38:2c:4a:e7:da:99  txqueuelen 1000  (Ethernet)
        RX packets 302937  bytes 375988871 (358.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 142409  bytes 27383874 (26.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 8826  bytes 7615687 (7.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8826  bytes 7615687 (7.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

outline-tun0: flags=4241<UP,POINTOPOINT,NOARP,MULTICAST>  mtu 1500
        inet 10.0.85.1  netmask 255.255.255.0  destination 10.0.85.1
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 500  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0