3 ms·
Total noob question, but I'll ask it anyway: is there any coding that has to be done to do HTTPS, or is it as simple as linking to the same page with https in t
by gchucky 17y ago
Total noob question, but I'll ask it anyway: is there any coding that has to be done to do HTTPS, or is it as simple as linking to the same page with https in the front?
- kgrin 17y agoThere's server configuration, but not "coding" as traditionally defined.
- steveklabnik 17y agoYou need to have an SSL certificate, and your webserver has to have the appropriate modules and such installed and accept requets on port 443.
- yan 17y agoI also feel that I should point out: Putting forms behind SSL does not absolve you of secure coding guidelines! SSL does not influence whether or not your webapp is vulnerable to traditional injection and logic flaw attacks.
- Ixiaus 17y agoWhile that is true, the OP said he was interested in learning more beyond just SQL injection etc... Which brings me to your second subject: logic flaw. That is probably the most common security flaw than anything else. It is been made worse by the fact that most "web developers" don't actually understand logic nor the full implications of structured programming. It is compounded by a lack of understanding system fundamentals too; it's quite common amongst developers I have met to not know why "0123" comes out as "83" in any scripting language built atop C (Python and PHP are popular examples). (Hint for those that don't know: C interprets integer literals with a leading zero as an Octal number).
- diN0bot 17y agohaha. this is so true. i have no doubts the biggest problems we'll face with early product iterations are our own bugs rather than malicious third parties :-) we'll do the best we can to get both fronts up to snuff before the general public gets a stab at us.