HTTP/1.1 400 Bad Request
Connection: close

登录 - NAStool

HTTP/1.1 200 OK
Server: gunicorn
Date: Mon, 17 Feb 2025 22:37:57 GMT
Connection: keep-alive
Content-Type: text/html; charset=utf-8
Content-Length: 441903
Vary: Accept-Encoding, Cookie

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:pub="http://schemas.microsoft.com/windows/pub/2005/07" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:un0="http://schemas.microsoft.com/windows/pnpx/2005/10"><soap:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches</wsa:Action><wsa:MessageID>urn:uuid:3be5ec4c-b87d-4671-901d-e8960d25bb42</wsa:MessageID><wsa:RelatesTo>18930069-880c-41b3-886c-4ae76fac6b47</wsa:RelatesTo><wsd:AppSequence InstanceId="1734822275" SequenceId="urn:uuid:3d321c3f-3b84-4ae8-a170-3ace04b23eab" MessageNumber="7525"/></soap:Header><soap:Body><wsd:ProbeMatches><wsd:ProbeMatch><wsa:EndpointReference><wsa:Address>urn:uuid:6a8ef13d-6376-4b14-92a1-5c5a51d796b9</wsa:Address></wsa:EndpointReference><wsd:Types>wsdp:Device pub:Computer</wsd:Types><wsd:XAddrs>http://Jy-nas:5357/6a8ef13d-6376-4b14-92a1-5c5a51d796b9</wsd:XAddrs><wsd:MetadataVersion>2</wsd:MetadataVersion></wsd:ProbeMatch></wsd:ProbeMatches></soap:Body></soap:Envelope>

nginx

Jy-nas - Synology NAS

HTTP/1.1 200 OK
Server: nginx
Date: Tue, 18 Feb 2025 17:22:26 GMT
Content-Type: text/html; charset="UTF-8"
Transfer-Encoding: chunked
Connection: keep-alive
Keep-Alive: timeout=20
Vary: Accept-Encoding
Cache-control: no-store
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Content-Security-Policy: base-uri 'self';  connect-src data: ws: wss: http: https:; default-src 'self' 'unsafe-eval' data: blob: https://*.synology.com https://www.synology.cn/ https://help.synology.cn/; font-src 'self' data: https://*.googleapis.com https://*.gstatic.com; form-action 'self'; frame-ancestors 'self'; frame-src 'self' data: blob: https://*.synology.com https://*.synology.cn http://*.synology.com http://*.synology.cn http://global.synologydownload.com https://global.synologydownload.com; img-src 'self' data: blob: https://*.google.com https://*.googleapis.com http://*.googlecode.com https://*.gstatic.com https://global.download.synology.com; media-src 'self' data: about: https://*.synology.com https://help.synology.cn;  script-src 'self' 'unsafe-eval' data: blob: https://maps.google.com https://maps.googleapis.com https://ajax.googleapis.com https://help.synology.com https://help.synology.cn; style-src 'self' 'unsafe-inline' https://*.googleapis.com;


Synology DiskStation Manager (DSM):
  Version: 7.2.1-69057
  Hostname: Jy-nas

HTTP/1.1 404 Not Found
Date: Sat, 22 Feb 2025 19:31:21 GMT
Server: Apache
Content-Length: 196
Content-Type: text/html; charset=iso-8859-1

nginx

HTTP/1.1 502 Bad Gateway
Server: nginx
Date: Sun, 16 Feb 2025 03:45:09 GMT
Content-Type: text/html
Content-Length: 552
Connection: keep-alive
Keep-Alive: timeout=20

-DENIED Redis is running in protected mode because protected mode is enabled and no password is set for the default user. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 4) Set up an authentication password for the default user. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.

HTTP/1.1 404 Not Found
SERVER: Linux/4.4.302+, UPnP/1.0, Portable SDK for UPnP devices/1.12.1
CONNECTION: close
CONTENT-LENGTH: 48
Accept-Ranges: bytes
CONTENT-TYPE: text/html