@[email protected] to Ask [email protected] • 1 year agoWhat's a company secret you can share now that you no longer work there?message-square927fedilinkarrow-up11.13K
arrow-up11.12Kmessage-squareWhat's a company secret you can share now that you no longer work there?@[email protected] to Ask [email protected] • 1 year agomessage-square927fedilink
minus-square@[email protected]linkfedilink7•1 year agoI’m not 100% on this but I think GET requests are logged by default. POST requests, normally used for passwords, don’t get logged by default. BUT the Uri would get logged would get logged on both, so if the URI contained @username:Password then it’s likely all there in the logs
minus-square@[email protected]linkfedilink2•1 year agoGet and post requests are logged The difference is that the logged get requests will also include any query params GET /some/uri?user=Alpha&pass=bravo While a post request will have those same params sent as part of a form body request. Those aren’t logged and so it would look like this POST /some/uri
minus-square@[email protected]linkfedilinkEnglish1•1 year ago GET requests are logged That’s why I specified the receiving web server doesn’t log the URI in my question.
I’m not 100% on this but I think GET requests are logged by default.
POST requests, normally used for passwords, don’t get logged by default.
BUT the Uri would get logged would get logged on both, so if the URI contained @username:Password then it’s likely all there in the logs
Get and post requests are logged
The difference is that the logged get requests will also include any query params
GET /some/uri?user=Alpha&pass=bravo
While a post request will have those same params sent as part of a form body request. Those aren’t logged and so it would look like this
POST /some/uri
That’s why I specified
in my question.