Closed benoitm974 closed 1 year ago
Preview of the website obtained from the PR: https://51e10ca2.hack-gpon-preview.pages.dev
can we have an example of a problem?
Sure I have a case on my openwrt curl version below with and without the accept-language option
root@OpenWrt:~# curl -i -s -k -X $'POST' -H $'Accept-Language: en-GB,en-US;q=0.9,en;q=0.8' -d $'ploam_password=00000XXXXXXXXXXX' $'http://192.168.100.1/ONT/client/data/R outer.json' HTTP/1.0 200 OK Cache-Control: no-cache,no-store,max-age=0 Prama: no-cache X-Frame-Options: DENY Expires: 0 X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block CONTENT-LANGUAGE: en-GB,en-US;q=0.9,en;q=0.8 Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval'
curl -i -k -X $'POST' -d $'ploam_password=00000XXXXXXXXXXX' $'http://192.168.100.1/ONT/client/data/Router.json' curl: (1) Received HTTP/0.9 when not allowed
(i just removed the -s so the error is shown), the HTTP/0.9 is very wired but it seems the sercomm mini_httpd with this curl don't match... I think adding it would make compatibility easier for every one.
Adding the Accept-Language header back since it creates issue for some case/users