Hello, in this video, we are going to extend our example of using CGI for the get method for the POST method. And honestly, it's really simple. The Python file where you get data doesn't actually change in some languages, you would have to change the type PHP. All you do, you go here, change this post, and you're done. So here, as you can see, in the get format, he sent it via the URL, we go back to the file, get file dot html, and if I type in something slightly different, click Submit. I think he still printed it.
We signed the URL, he sent it via the POST method. That's the only difference that's all it is. And you know, all these these two videos this one the previous longer WE DIDN'T GET and POST methods, yet we only covered in a very simple form, you know, basically text a forms animal In other sorts of text every checkbox checkbox radio buttons all other sorts of analyses the principle is exactly the same what I'll do is provided link with both of these videos so you can actually see how to access them but honestly if you can get your head around doing get imposed with what we've done with this example euro go to them before we finish our hands and go over the differences between GET and POST so get because the value stay in the URL they great for stuff like bookmarking that history. So post is doing the same thing and it's not bookmarked the Back button so when you click Back button, the Back button, get requests are re executed on may not be resubmitted to serve that is HDMI stored in the browser cache.
Where it's supposed to be brother usually alerts the user that data will need to be resubmitted So that's something to bear in mind what we might already see that when you click back, and you may have submitted a form, I say, do you want to resubmit the data again, and the encoding type is slightly different. So check that out a bit more parameters. Let's look at that. And since I can send, you know, parameter data, but it's limited to what we can have in the URL, and you can only have so much clip really depends on the drivers character limit, and they have different catalysts, then on top of that, you URL will vary in sizes like this is localhost. But you might have a www dot before moving HTTP, you know, as all of that stuff, and we might have a routing system as well.
So I've seen brother that can go up to like the fan and 24 characters or more or less, and the safest amount is to use two K or parameters and is some server can handle 64 but it's not recommended to use a lot and For post, you can send a lot so much you can even upload files. Okay? So from a hacking perspective, easy jack, get it very, very because it's just in the URL. So you can change that. So you can easily manipulate that post very difficult. Okay, so restrictions on the sort of home data that you can submit, in, get, you can only submit ASCII characters, and in post, really no restriction.
But in binary data, it also allowed if you really want to go down that route security get in less secure compared to both because data center plot you're also saving Bradley's re answer logs and plaintext with post is more safe than get because the parameter, you know, are not stored in Brandon's field server logs and further restrictions on the full length. Some people say like 248 you know, the good format, I would say honestly, don't go crazy with it because you know, different browsers, different restrictions, and no restrictions on poses during the release. So okay, usability and get method should not be used when sending passwords or sensitive information. So definitely no post when sending passwords and things mentioned, pretty simple visibility, you know, everyone can see get because you know, it's hidden. I mean, it's displayed in the URL post, really, no one can be hidden.
So caching, get can be cached, post can be cut. So those are the differences between it. Obviously, you can go into the difference of differences a lot more, you could spend days and days just going into the technical aspects of the difference in between get posts and how they work. And honestly, there's no evil solution that you'll use for your website. You'll use one for a certain scenario and one for another scenario. That's it for this video.
Thanks for watching. I look forward to seeing you in the next Python demo.