Recent content by jefcolbi

  1. J

    Bughost not fully working

    as explained, earlier i already massively tested different payloads and only one payload pass the dpi and return http 200 but the data are blocked after sometimes. So this doesn't simply work. and my operator block even tls hello client.
  2. J

    Bughost not fully working

    Ah not really. i am trying the facebook proxy path, but looks like each connection is capped at 300KB. can't open heavy websites with that like github
  3. J

    Bughost not fully working

    well no. it is what i am using to write you. it is fine. I simulated a recorded request from facebook with a test websocket server WITH WORKING INTERNET WIFI === Handshake request sent === 'GET /ws/XXXXXXXXXX?lid=XXXXXXXXXXHTTP/1.1\r\nAccept-Encoding: gzip, deflate, br...
  4. J

    Bughost not fully working

    my proxy is not a normal proxy bro. it is a test proxy that return the initial http 200 response and continuously send data to the client to verify the connection can be maintained. for now the test proxy can return data for only 60s limited to 35KB. that is it. There is not a know pattern why...
  5. J

    Bughost not fully working

    so here are the results GET / HTTP/1.1[crlf]Host: 0.freebasics.com[crlf][crlf] -> brutal fails/stop CONNECT [host_port] .HTTP/1.0[crlf]Host: 0.freebasics.com[crlf][crlf] -> brutal fails/stop CONNECT [host_port] SHTTP/1.0 200 OK HTTP/1.0[crlf]Host: 0.freebasics.com[crlf][crlf] -> stuck...
  6. J

    Bughost not fully working

    Yes. but you are not understanding that even with a WORKING internet connection droidvpn doesn't work. http and tcp don't work at all. port 80 or 443. it stops after "socket connected"
  7. J

    Bughost not fully working

    the header will not work. as i stated the remote proxy can reply only when there is no space between the http and the http protocol example GET 8.8.8.8HTTP/1.1 ...
  8. J

    Bughost not fully working

    i already changed it to 443 before replying to you. and again i tried to connect first with a working internet. i doubt that if it doesn't work with fully working internet it will do without it.
  9. J

    Bughost not fully working

    I tested first with a working internet connection. TCP & HTTP doesn't reach the "invalid username and password" for all servers. only UDP & ICMP do
  10. J

    Bughost not fully working

    So here is the result of the payload you gave, the server can return HTTP 200 but the data sent after are blocked Server logs b'CONNECT 37.59.121.117:443 HTTP:www.lazada.com.ph' 1774706120.8091583 Sent 281 to <socket.socket fd=10, family=2, type=1, proto=0, laddr=('X.X.X.X', 3128)...
  11. J

    Bughost not fully working

    Hi. Can you point me to the OHP server you are refering to? Also i am myself a developer. So i did a TCP server which always return "HTTP/1.1 200 Connection Established\r\nConnection: Keep-Alive\r\n\r\n" and start send sending some data from only the tcp server. when i send binary data they...
  12. J

    Bughost not fully working

    I have a bughost which partially works. I need some advices. Here is a json of the payload and the response { "timestamp": "2026-03-27 03:29:56", "target_host": "37.59.121.117", "target_port": 443, "proxy_host": "X.X.X.X", "proxy_port": 80, "mode": "proxy", "variant": "legacy", "status_code"...
Back
Top