On 3/13/25 21:38, Zahid Rahman wrote:
That's my point , the majority of websites must be hosted without a proxy
server in front leaving the codebase vulnerable to attack.
I was just wondering 🤔 the number of vulnerable websites in percentage
terms ?
My pages are presently off. I do not know about the present thread, but
when up, it took daily maintenance to keep it up. 3 reasons, 1, most of
the spiders that feed their search engines ignore your robots.txt. 2,
more of them also will download the tail end of your 30 gigabytes of
pictures on a slow, cheap adsl circuit, and immediately start to reload,
using up your upload bandwidth to the point apache can't get a 4 letter
word back to someone who might be interested in seeing what your site
has to offer. 3. it takes about an hour a day to stay ahead of such
jerks because they can see they are being blocked by iptables or a clone
of it and will swap the machine being an ass to a different address.
Major srcs of such bs often resolve to as much as 24 bits of an ipv4
address, so I've had iptables rules /25 bits wide.
¯\_(ツ)_/¯
♡۶♡ ۶♡۶
<http://www.backbutton.co.uk>
On Thu, 13 Mar 2025, 19:18 Frank Gingras, <thu...@apache.org> wrote:
On Thu, Mar 13, 2025 at 1:53 PM Zahid Rahman <zahidr1...@gmail.com> wrote:
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?
No, that's not what a proxy means. Proxying content means using another
server/backend to serve the contents.
What you are describing is just being a hosting provider.
Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org