CaspianXI@lemmy.world to Ask Lemmy@lemmy.world · 1 year agoWhat's a company secret you can share now that you no longer work there?message-squaremessage-square969fedilinkarrow-up11.35Karrow-down115
arrow-up11.34Karrow-down1message-squareWhat's a company secret you can share now that you no longer work there?CaspianXI@lemmy.world to Ask Lemmy@lemmy.world · 1 year agomessage-square969fedilink
minus-squareItsMyFirstDay@lemmy.worldlinkfedilinkarrow-up10·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-squareSzethFriendOfNimi@lemmy.worldlinkfedilinkarrow-up2·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
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