The usual routine when hosting a website is :- One is given access to the apache webserver via filezilla whereby the locally tested code from local machine is uploaded using ftp port 22.
The code is then served by the apache webserver via port 80. If this is the routine followed by most hosting companies and front end developers , then are most apache webservers not acting as proxies but as webservers ? ¯\_(ツ)_/¯ ♡۶♡ ۶♡۶ <http://www.backbutton.co.uk> On Thu, 13 Mar 2025, 16:13 Frank Gingras, <thu...@apache.org> wrote: > > > On Thu, Mar 13, 2025 at 11:22 AM Zahid Rahman <zahidr1...@gmail.com> > wrote: > >> Serving codebase directly means setting up an index.html file in the >> config directory on the same disk as the apache install as per >> these instructions >> >> >> https://documentation.ubuntu.com/server/how-to/web-services/install-apache2/index.html >> >> >> >> ¯\_(ツ)_/¯ >> ♡۶♡ ۶♡۶ >> >> <http://www.backbutton.co.uk> >> >> On Thu, 13 Mar 2025, 14:51 Frank Gingras, <thu...@apache.org> wrote: >> >>> >>> >>> On Thu, Mar 13, 2025 at 10:43 AM Zahid Rahman <zahidr1...@gmail.com> >>> wrote: >>> >>>> Hi, >>>> >>>> Do the majority of apache webservers made available by web hosting >>>> companies at their data centres serve codebase directly or are the >>>> majority act as proxy servers ? >>>> >>>> Thanks in advanced for sharing . >>>> >>>> >>>> >>>> ¯\_(ツ)_/¯ >>>> ♡۶♡ ۶♡۶ >>>> >>> >>> What does "serve codebase directly" mean here, exactly? >>> >> > In that case, it depends on how the administrator configured their server. > > In most cases, they will give you control over your content, and you can > choose to proxy, or not. > > As well, some may use horizontal scaling or similar approaches; you will > need to ask the hoster what they use. > > What is the actual question, or problem you're trying to solve here? >