canpolat@programming.dev to Programming@programming.devEnglish · 1 month agoYour API Shouldn't Redirect HTTP to HTTPSjviide.iki.fiexternal-linkmessage-square13fedilinkarrow-up1109arrow-down14cross-posted to: hackernews@lemmy.smeargle.fans
arrow-up1105arrow-down1external-linkYour API Shouldn't Redirect HTTP to HTTPSjviide.iki.ficanpolat@programming.dev to Programming@programming.devEnglish · 1 month agomessage-square13fedilinkcross-posted to: hackernews@lemmy.smeargle.fans
minus-squarevithigar@lemmy.calinkfedilinkarrow-up47arrow-down1·edit-21 month agoThis article isn’t about browsers or websites, and even acknowledges in the opening that it makes sense as a usability tradeoff in that context.
minus-squarev9CYKjLeia10dZpz88iU@programming.devlinkfedilinkarrow-up18arrow-down4·1 month agoI clearly didn’t read it. It makes sense, if users aren’t visiting the API then it really doesn’t matter that it’s not redirected on insecure connections.
minus-squarepinchcramp@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up10arrow-down1·edit-21 month ago I clearly didn’t read it. I love the honesty. It’s really refreshing to see someone take accountability instead of becoming defensive.
This article isn’t about browsers or websites, and even acknowledges in the opening that it makes sense as a usability tradeoff in that context.
I clearly didn’t read it. It makes sense, if users aren’t visiting the API then it really doesn’t matter that it’s not redirected on insecure connections.
I love the honesty. It’s really refreshing to see someone take accountability instead of becoming defensive.