The Hypertext Transfer Protocol (HTTP) is designed to enable communications between clients and servers.<\/p>\n\n\n\n
HTTP works as a request-response protocol between a client and server.<\/p>\n\n\n\n
A web browser may be the client, and an application on a computer that hosts a web site may be the server.<\/p>\n\n\n\n
A client (browser) submits an HTTP request to the server; then the server returns a response to the client.<\/p>\n\n\n\n
A client (browser) submits an HTTP request to the server; then the server returns a response to the client. The response contains status information about the request and may also contain the requested content.<\/p>\n\n\n\n
There are two ways the browser client can send information to the web server. The GET method sends the encoded user information appended to the page request. The page and the encoded information are separated by the ? character.<\/p>\n\n\n\n http:\/\/www.tutorialsclass.com\/index.htm?name1=value1&name2=value2<\/p>\n\n\n\n GET requests can be cached The POST method transfers information via HTTP headers. The information is encoded as described in case of GET method and put into a header called The POST method does not have any restriction on data size to be sent.<\/p>\n\n\n\n The POST method can be used to send ASCII as well as binary data.<\/p>\n\n\n\n The data sent by POST method goes through HTTP header so security depends on HTTP protocol. By using Secure HTTP you can make sure that your information is secure.<\/p>\n\n\n\n The PHP provides Since the data sent by the GET method are displayed in the URL, it is possible to bookmark the page with specific query string values. HTTP The Hypertext Transfer Protocol (HTTP) is designed to enable communications between clients and servers. HTTP works as a request-response protocol between a client and server. A web browser may be the…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"footnotes":""},"faq_type":[122],"keywords":[],"class_list":["post-6166","faq","type-faq","status-publish","hentry","faq_type-all-php-interview-questions-answers"],"yoast_head":"\nGET <\/code>– Requests data from a specified resourcePOST<\/code> – Submits data to be processed to a specified resource<\/p>\n\n\n\n
\n\n\n\nGET Method<\/h3>\n\n\n\n
GET requests remain in the browser history
GET requests can be bookmarked
GET requests should never be used when dealing with sensitive data
GET requests have length restrictions
GET requests should be used only to retrieve data<\/p>\n\n\n\n<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <title>Example of PHP GET method<\/title>\n<\/head>\n<body>\n<?php\nif(isset($_GET[\"name\"])){\n echo \"<p>Hi, \" . $_GET[\"name\"] . \"<\/p>\";\n}\n?>\n<form method=\"get\" action=\"<?php echo $_SERVER[\"PHP_SELF\"];?>\">\n <label for=\"inputName\">Name:<\/label>\n <input type=\"text\" name=\"name\" id=\"inputName\">\n <input type=\"submit\" value=\"Submit\">\n<\/form>\n<\/body><\/code><\/pre>\n\n\n\n
\n\n\n\nPOST Method<\/h3>\n\n\n\n
QUERY_STRING.<\/code><\/p>\n\n\n\n$_POST<\/code> associative array to access all the sent information using POST method.<\/p>\n\n\n\n<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <title>Example of PHP POST method<\/title>\n<\/head>\n<body>\n<?php\nif(isset($_POST[\"name\"])){\n echo \"<p>Hi, \" . $_POST[\"name\"] . \"<\/p>\";\n}\n?>\n<form method=\"post\" action=\"<?php echo $_SERVER[\"PHP_SELF\"];?>\">\n <label for=\"inputName\">Name:<\/label>\n <input type=\"text\" name=\"name\" id=\"inputName\">\n <input type=\"submit\" value=\"Submit\">\n<\/form>\n<\/body><\/code><\/pre>\n\n\n\n
\n\n\n\nAdvantages and Disadvantages of Using the GET Method<\/h3>\n\n\n\n
The GET method is not suitable for passing sensitive information such as the username and password, because these are fully visible in the URL query string as well as potentially stored in the client browser’s memory as a visited page.
Because the GET method assigns data to a server environment variable, the length of the URL is limited. So, there is a limitation for the total data to be sent.<\/p>\n\n\n\n
\n\n\n\nGET vs. POST<\/h3>\n\n\n\n
<\/th> GET<\/th> POST<\/th><\/tr> BACK button\/Reload<\/td> Harmless<\/td> Data will be re-submitted\n(the browser should alert the user that\nthe data are about to be re-submitted)<\/td><\/tr> Bookmarked<\/td> Can be bookmarked<\/td> Cannot be bookmarked<\/td><\/tr> Cached<\/td> Can be cached<\/td> Not cached<\/td><\/tr> Encoding type<\/td> application\/x-www-form-urlencoded<\/td> application\/x-www-form-urlencoded or multipart\/form-data.\nUse multipart encoding for binary data<\/td><\/tr> History<\/td> Parameters remain in browser history<\/td> Parameters are not saved in browser history<\/td><\/tr> Restrictions on data length<\/td> Yes, when sending data,\nthe GET method adds the data to the URL;\nand the length of a URL is limited\n(maximum URL length is 2048 characters)<\/td> No restrictions<\/td><\/tr> Restrictions on data type<\/td> Only ASCII characters allowed<\/td> No restrictions. Binary data is also allowed<\/td><\/tr> Security<\/td> GET is less compared to\nPOST data sent is part of URL<\/td> POST is a little safer than GET because\nthe parameters are not stored\nin browser history or in web server logs<\/td><\/tr> Visibility<\/td> Data is visible to everyone in the URL<\/td> Data is not displayed in the URL<\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"