[DiscordArchive] oh u pinging the 'rest' connection?
[DiscordArchive] oh u pinging the 'rest' connection?
Original source
oh u pinging the 'rest' connection?
rektbyfaith
10-25-2025, 08:28 PM #1Archived author: Fabian • Posted: 2025-10-25T20:28:33.741000+00:00
Original source
oh u pinging the 'rest' connection?
Original source
Oh wow thats work thx
```
❯ time curl -Ikv http://192.168.178.169:8081
* Trying 192.168.178.169:8081...
* Connected to 192.168.178.169 (192.168.178.169) port 8081 (#0)
> HEAD / HTTP/1.1
> Host: 192.168.178.169:8081
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
< Set-Cookie: JSESSIONID=4a60fec6-8d78-3162-ad47-0476deb6db78; Path=/bnetserver; Domain=192.168.178.169; Secure; HttpOnly; SameSite=None
Set-Cookie: JSESSIONID=4a60fec6-8d78-3162-ad47-0476deb6db78; Path=/bnetserver; Domain=192.168.178.169; Secure; HttpOnly; SameSite=None
< Date: Sat, 25 Oct 2025 18:29:01.3620711 GMT
Date: Sat, 25 Oct 2025 18:29:01.3620711 GMT
< Server: Boost.Beast/322
Server: Boost.Beast/322
< Content-Length: 0
Content-Length: 0
<
* Connection #0 to host 192.168.178.169 left intact
curl -Ikv http://192.168.178.169:8081 0.00s user 0.00s system 13% cpu 0.032 total
```
rektbyfaith
10-25-2025, 08:29 PM #2Archived author: Luzifix • Posted: 2025-10-25T20:29:23.234000+00:00
Original source
Oh wow thats work thx
```
❯ time curl -Ikv http://192.168.178.169:8081
* Trying 192.168.178.169:8081...
* Connected to 192.168.178.169 (192.168.178.169) port 8081 (#0)
> HEAD / HTTP/1.1
> Host: 192.168.178.169:8081
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
< Set-Cookie: JSESSIONID=4a60fec6-8d78-3162-ad47-0476deb6db78; Path=/bnetserver; Domain=192.168.178.169; Secure; HttpOnly; SameSite=None
Set-Cookie: JSESSIONID=4a60fec6-8d78-3162-ad47-0476deb6db78; Path=/bnetserver; Domain=192.168.178.169; Secure; HttpOnly; SameSite=None
< Date: Sat, 25 Oct 2025 18:29:01.3620711 GMT
Date: Sat, 25 Oct 2025 18:29:01.3620711 GMT
< Server: Boost.Beast/322
Server: Boost.Beast/322
< Content-Length: 0
Content-Length: 0
<
* Connection #0 to host 192.168.178.169 left intact
curl -Ikv http://192.168.178.169:8081 0.00s user 0.00s system 13% cpu 0.032 total
```
Original source
on 9.2.7 it was https with a invalid cert^^
rektbyfaith
10-25-2025, 08:29 PM #3Archived author: Luzifix • Posted: 2025-10-25T20:29:43.686000+00:00
Original source
on 9.2.7 it was https with a invalid cert^^
Original source
yeah modern client really dislikes https with that cert, it doesnt work anymore
rektbyfaith
10-25-2025, 08:30 PM #4Archived author: Tea • Posted: 2025-10-25T20:30:17.322000+00:00
Original source
yeah modern client really dislikes https with that cert, it doesnt work anymore
Original source
*https on the rest connection
rektbyfaith
10-25-2025, 08:30 PM #5Archived author: Tea • Posted: 2025-10-25T20:30:45.293000+00:00
Original source
*https on the rest connection
Original source
the initial one has no problems
rektbyfaith
10-25-2025, 08:30 PM #6Archived author: Tea • Posted: 2025-10-25T20:30:51.774000+00:00
Original source
the initial one has no problems
Original source
Ok, thx now i know how to call it correctly
rektbyfaith
10-25-2025, 08:31 PM #7Archived author: Luzifix • Posted: 2025-10-25T20:31:16.146000+00:00
Original source
Ok, thx now i know how to call it correctly
Original source
yes
rektbyfaith
10-25-2025, 08:31 PM #8Archived author: Luzifix • Posted: 2025-10-25T20:31:43.874000+00:00
Original source
yes
1 Guest(s)
1 Guest(s)