03-09-2018
Quote:
Originally Posted by
hicksd8
On a client on which WP2 loads "super-slow" what happens if you put WP2's IP address in the URL instead of its hostname? Let's prove that the slowness is not a problem in resolving the name.
Also, if you ping WP2 from that client using first the hostname and second the IP address is the response the same speed-wise?
I attached an image of what i am trying to do in my original post.
Anyway, using the IP from the DMZ server to the WP1 & WP2 have no difference in speed. WP1 loads fine, WP2 loads very slow
---------- Post updated at 01:31 PM ---------- Previous update was at 01:21 PM ----------
Quote:
Originally Posted by
gull04
Hi,
I think I would start with some basics here assuming that the IP's are different, you could try;
- Ping the IP Addresses from your work station, check that they are around the same.
- Ping the URL for each and look for obvious differences to the IP Address pings.
- Run a traceroute from each and look for differences.
- Check and make sure that the reverse lookup is the same.
You could also look at things like the network config, between the switches if they are physically different.
It would also be worth looking at the /etc/network/interfaces file on the proxy.
There are just so many possibilities here, it will have to be a process of elimination.
Regards
Gull04
ping & traceroute blocked between networks here, sorry.
Network A these servers are all VMs and on the same subnet.
9 More Discussions You Might Find Interesting
1. Linux
I have configured reverse proxy through apache...conf file is attached
My reverse proxy has a public ip.it is redirecting the request to 172.16.1.43 which is http
server.....Now i have a link in Http server's home page which will redirect the request to
another Lan zone machine... (0 Replies)
Discussion started by: dipanrc
0 Replies
2. UNIX for Dummies Questions & Answers
Hi
I am trying to set up two hosts in a reverse proxy. The reverse proxy already has 8 servers running perfectly, but they are all simply mapping pure addresses, which I have registered internally and externally.
The latest two I wish to add are a bit different, they are app servers, one... (1 Reply)
Discussion started by: rboekdrukker
1 Replies
3. IP Networking
Hi,
I am involved in a project on Debian. One of my requirement is to route an IP packet in my application to a proxy server and receive the reply from the proxy server as an IP packet. My application handles data at the IP frame level. My application creates an IP packet(with all the necessary... (0 Replies)
Discussion started by: Rajesh_BK
0 Replies
4. UNIX for Advanced & Expert Users
I'd just like to know what you use for user account management on your DMZ servers?
Do you use the same authentication realm as internally?
Do you use a different authentication realm, perhaps only for the DMZ?
Do you use local accounts? (2 Replies)
Discussion started by: humbletech99
2 Replies
5. UNIX for Advanced & Expert Users
Hi All,
I have a webpage loaded on server1 with authorization enabled by .htaccess, which can be accessed by http://ipofserver1/index.html. Now im planning a high availabilty load balancing in such a way that if the server1 is down due to some reason it should connect to another server. i have... (1 Reply)
Discussion started by: Tuxidow
1 Replies
6. UNIX for Advanced & Expert Users
Hi all,
The scenario is:
http://img834.imageshack.us/img834/7990/1234z.jpg
- With:
+ 192.168.100.0/24 : internet link (simulation)
+ Multiple Websites are hosting in local.
+ Complete DNS configuration.
+ OS: CentOS 5
- Requirements:
Configure Squid Proxy as... (0 Replies)
Discussion started by: kidzer0
0 Replies
7. Web Development
Reading Apache documentation I come to understand that it can host different websites, either by FQDN or IP address, virtually.
Is it possible for an Apache server to run two sites, and no one be able to tell from outside, that they are hosted in the same server? If not possible.
Essentially,... (2 Replies)
Discussion started by: Aia
2 Replies
8. Red Hat
Hi All
I need your valuable help on this. Im trying to setup reverse proxy using apache in rhel 5.5. I just started with Apache, and not much idea about going with advance level config, except that i have tried to set up this reverse proxy based on an online guide i found in internet. The... (0 Replies)
Discussion started by: niyas_gk
0 Replies
9. IP Networking
Hi, one member of WJ forum adviced that i setup an reverse proxy for my webserver. So im curious if anyone know about good, easy noob tutorial on hwo to achieve this, please link to this tutorial how to setup reverse proxy for an webserver.
Or better for whole node server with OpenVZ... (1 Reply)
Discussion started by: postcd
1 Replies
LEARN ABOUT DEBIAN
catalyst::manual::deployment
Catalyst::Manual::Deployment(3pm) User Contributed Perl Documentation Catalyst::Manual::Deployment(3pm)
NAME
Catalyst::Manual::Deployment - Deploying Catalyst
DEPLOYMENT OPTIONS
Catalyst applications are most often deployed as a FastCGI or mod_perl application (with FastCGI being the recommended option). However, as
Catalyst is based on the PSGI specification, any web handler implementing that specification can be used to run Catalyst applications.
This documentation most thoroughly covers the normal and traditional deployment options, but will mention alternate methods of deployment,
and we welcome additional documentation from people deploying Catalyst in non-standard environments.
Deployment in a shared hosting environment
Almost all shared hosting environments involve deploying Catalyst as a FastCGI application on Apache. You will usually want to have a set
of libraries specific to your application installed on your shared host.
Full details of deploying Catalyst in a shared hosting environment are at Catalyst::Manual::Deployment::SharedHosting.
FastCGI
FastCGI is the most common Catalyst deployment option. It is documented generally in Catalyst::Manual::Deployment::FastCGI, and there are
specific instructions for using FastCGI with common web servers below:
Apache
Catalyst::Manual::Deployment::Apache::FastCGI
nginx
Catalyst::Manual::Deployment::nginx::FastCGI
lighttpd
Catalyst::Manual::Deployment::lighttpd::FastCGI
Microsoft IIS
Catalyst::Manual::Deployment::IIS::FastCGI
mod_perl
Traditionally a common deployment option for dedicated applications, mod_perl has some advantages and disadvantages over FastCGI. Use of
mod_perl is documented in Catalyst::Manual::Deployment::Apache::mod_perl.
Development Server
It is possible to deploy the Catalyst development server behind a reverse proxy. This may work well for small-scale applications which are
in an early development phase, but which you want to be able to show to people. See Catalyst::Manual::Deployment::DevelopmentServer.
PSGI
Catalyst can be deployed with any PSGI-compliant handler. See Catalyst::PSGI for more information; a list of possible deployment servers
are shown below:
Starman
Starman is a high-performance Perl server implementation, which is designed to be used directly (rather than behind a reverse proxy). It
includes HTTP/1.1 support, chunked requests and responses, keep-alive, and pipeline requests.
Starlet
Starlet is a standalone HTTP/1.0 server with keepaXXalive support which is suitable for running HTTP application servers behind a reverse
proxy.
Twiggy
Twiggy is a high-performance asynchronous web server. It can be used in conjunction with Catalyst, but there are a number of caveats which
mean that it is not suitable for most deployments.
Chef
<LChef|http://www.opscode.com/chef/> is an open-source systems integration framework built specifically for automating cloud computing
deployments. A Cookbooks demonstrating how to deploy a Catalyst application using Chef is available at
<http://community.opscode.com/cookbooks/catalyst> and http://github.com/melezhik/cookbooks/wiki/Catalyst-cookbook-intro
<http://github.com/melezhik/cookbooks/wiki/Catalyst-cookbook-intro>.
AUTHORS
Catalyst Contributors, see Catalyst.pm
COPYRIGHT
This library is free software. You can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.14.2 2012-01-20 Catalyst::Manual::Deployment(3pm)