Techgalery.com by @adm.uiux

  Web application server stack Apache, PHP, MySQL I’ve just used GCP recently, so I created one Virtual machine, and as usual I try to develop my own web server manually as I always did in the old school ways, by using SSH. Although GCP has some tools for deploying button click web servers from the marketplace, for example LAMP, you can install those and your web server will be ready quickly, but i am not familiar with that so i decided to do the old ways. And besides, the prices of those marketplace solutions can be 5 times higher than if you just installed your own server stack by yourself. All the web application components are all open source and free from the Operating System (which i choose Debian 10), the web server (Apache), Database (MariaDB) and PHP. Except extra cost for Domain name and SSL. Turns out, I am still not that much familiar with bare metal web application development either. I still struggle to remember what to do, but I have the big picture so I can install ...

Apache PHP MySQL The  Hypertext Transfer Protocol (HTTP) response status is to indicate what the server return given the request that's being made by the client. This response codes is a standard which many web server vendor like Apache, Nginx or Microsoft IIS should follow in order to make it easier for the client side vendor understand the meaning of the response, client or agent for example Web browser such as Google Chrome, Mozilla Firefox, Safari, etc. 1. Informational responses (100–199) 100 Continue This interim response indicates that everything so far is OK and that the client should continue the request, or ignore the response if the request is already finished. 101 Switching Protocol This code is sent in response to an Upgrade request header from the client, and indicates the protocol the server is switching to. 102 Processing (WebDAV) This code indicates that the server has received and is processing the request, but no response is available yet. ...

Photo by Austin Distel on Unsplash To request resource using HTTP you must specify the HTTP Methods, HTTP have some set of request methods to indicate the action to be performed by the client and the server. Sometimes These request methods are referred as HTTP verbs, but can also be referred as nouns. Each of them implements a different semantic, but some common features are shared by a group of them: e.g. a request method can be safe, idempotent, or cacheable. Here's some HTTP methods you should know in order to understand the concept of HTTP process. GET The GET method requests a representation of the specified resource. Requests using GET should only retrieve data. HEAD The HEAD method asks for a response identical to that of a GET request, but without the response body. POST The POST method is used to submit an entity to the specified resource, often causing a change in state or side effects on the server. PUT The PUT method replaces all current repres...