Thanks for the response... I looked through my httpd.conf file and found
that the WebSpherePluginConfig was pointing to the wrong plugin directory (
the person who had originally installed WAS had forgotten to update the file
to point it to the right directory). I regenerated and propagated the
On Fri, Jul 10, 2009 at 12:39 PM, Chintan Kachhichintankac...@gmail.com wrote:
Thanks for the response... I looked through my httpd.conf file and found
that the WebSpherePluginConfig was pointing to the wrong plugin directory (
the person who had originally installed WAS had forgotten to update
Does that mean there is no way to do this? Maybe using rewrite module which
looks for the response and redirects it to a custom error page based on the
response? I think I came across a post where you mentioned something about
using modules look ahead feature. Is that possible?
On Fri, Jul 10,
Ok.. here's the thing:
I am having a issue, where the following happens: I am using IBM http server
as my front end server, and WebSphere as my application server.
I am trying to configure httpserver config file (httpd.conf) to display a
certain page when my application
server is down - but that
On Thu, Jul 9, 2009 at 11:23 AM, Chintan Kachhichintankac...@gmail.com wrote:
Ok.. here's the thing:
I am having a issue, where the following happens: I am using IBM http server
as my front end server, and WebSphere as my application server.
I am trying to configure httpserver config file
Chintan Kachhi chintankac...@gmail.com writes:
I am having a issue, where the following happens: I am using IBM http server
as
my front end server, and WebSphere as my application server.
I am trying to configure httpserver config file (httpd.conf) to display a
certain page when my
[To Dan Poirier] I need to go to Websphere to hit the service and that
requires the port 9080, hence I do that... but this should work and return
the error message I think since the http server is linked to the Websphere
through the plugin... someone correct me if I am wrong.
As for changing the
On Thu, Jul 9, 2009 at 3:48 PM, Chintan Kachhichintankac...@gmail.com wrote:
[To Dan Poirier] I need to go to Websphere to hit the service and that
requires the port 9080, hence I do that... but this should work and return
the error message I think since the http server is linked to the
Assuming your definition of down is not responding, there is no way
for the server to respond with any kind of status code. Your customer's
browsers will generally give them a message of some kind that it
couldn't contact the server , however as the web administrator you have
no visibility or
Thanks for the replies... I guess that can't be done then, but after
thinking a bit, I think that I am probably looking for the scenario where a
service is down on a server, rather than the server itself. Let's assume
that I get the following response when the service is down: HTTP/1.1 404 Not
Thanks for the link...I have looked through it before, and I just tried what
it says, and it works ( I can just put my custom message within the
httpd.conf file against the ErrorDocument 404 directive, and it will display
this message when the page cannot be found.).That's exactly the
On Mon, Jul 6, 2009 at 6:05 PM, Chintan Kachhichintankac...@gmail.com wrote:
All the person would
then have to do is to load the module, which would have the rewrite engine
turned on.. and boom, it would work.
Why would someone ever use the module if ErrorDocument is there?
--
Eric Covener
12 matches
Mail list logo
