A couple of years ago we were using our iSeries server as our HTTP
server ( V4R3 / V4R5 ).  After a while it was decided to move the HTTP
server to another platform and a HTML redirect page was put on the server
for any web browsers that still had the iSeries as the Home Page.  We are
now running V5R2 and I'm working with the Apache powered HTTP server.  I've
configured it properly, as per the Redbook.   I don't have any HTTP server
running except the default Apache server ( APACHEDFT ) and as a test I have
it listening to port 8022.  This works fine when I point the web browser to
{ ipaddress:8022 }.  When I change the listening port to 80 and connect
 {
ipaddress:80 } I still get the redirect happening, even though the old
server is long gone.  The folders I had in the IFS have been deleted, but
the redirect still happens.  If I change the configuration back so APACHEDFT
is listening to port 8022 ( it works the way it should ) and I point the web
browser to port 80, the redirect occurs.  Any ideas?

[ Post a follow-up to this message ]

looks like you are running two WebServers on your iSeries box. APACHEDFT and
another instance (that could be non-Apache classic) on port 80.

Try this: shut down APACHEDFT and try connecting to ipaddress:80. If a web
page is shown then a server is listening on port 80.

Sunit

"C G" <c.g@farmersdairy.ns.ca> wrote in message
news:c6lv0d$5r18$1@news.boulder.ibm.com...
>     A couple of years ago we were using our iSeries server as our HTTP
> server ( V4R3 / V4R5 ).  After a while it was decided to move the HTTP
> server to another platform and a HTML redirect page was put on the server
> for any web browsers that still had the iSeries as the Home Page.  We are
> now running V5R2 and I'm working with the Apache powered HTTP server.
I've
> configured it properly, as per the Redbook.   I don't have any HTTP server
> running except the default Apache server ( APACHEDFT ) and as a test I
have
> it listening to port 8022.  This works fine when I point the web browser
to
> { ipaddress:8022 }.  When I change the listening port to 80 and conne
ct {
> ipaddress:80 } I still get the redirect happening, even though the old
> server is long gone.  The folders I had in the IFS have been deleted, but
> the redirect still happens.  If I change the configuration back so
APACHEDFT
> is listening to port 8022 ( it works the way it should ) and I point the
web
> browser to port 80, the redirect occurs.  Any ideas?
>
>

[ Post a follow-up to this message ]

Thanks for the reply.  I tried that and the redirect didn't work.  As
soon as I started APACHEDFT on port 8022, port 80 started to redirect again.
I had ADMIN active under QHTTPSVR ( WRKACTJOB ), but I shut it down too and
only have APACHEDFT running now.  I've even tried setting up a new server,
other than APACHEDFT and I run in to the same issue.


"Sunit Patke" <supatke@nospam.com> wrote in message
news:c6m6pd$5nn4$1@news.boulder.ibm.com...
> looks like you are running two WebServers on your iSeries box. APACHEDFT
and
> another instance (that could be non-Apache classic) on port 80.
>
> Try this: shut down APACHEDFT and try connecting to ipaddress:80. If a web
> page is shown then a server is listening on port 80.
>
> Sunit
>
> "C G" <c.g@farmersdairy.ns.ca> wrote in message
> news:c6lv0d$5r18$1@news.boulder.ibm.com... 
server[vbcol=seagreen] 
are[vbcol=seagreen] 
> I've 
server[vbcol=seagreen] 
> have 
> to 
{[vbcol=seagreen] 
but[vbcol=seagreen] 
> APACHEDFT 
> web 
>
>

[ Post a follow-up to this message ]

Is it possible for you to post your httpd.conf file?

Sunit

"C G" <c.g@farmersdairy.ns.ca> wrote in message
news:c6m8rc$66no$1@news.boulder.ibm.com...
>     Thanks for the reply.  I tried that and the redirect didn't work.  As
> soon as I started APACHEDFT on port 8022, port 80 started to redirect
again.
> I had ADMIN active under QHTTPSVR ( WRKACTJOB ), but I shut it down too
and
> only have APACHEDFT running now.  I've even tried setting up a new server,
> other than APACHEDFT and I run in to the same issue.
>
>
> "Sunit Patke" <supatke@nospam.com> wrote in message
> news:c6m6pd$5nn4$1@news.boulder.ibm.com... 
> and 
web[vbcol=seagreen] 
> server 
> are 
> server 
browser[vbcol=seagreen] 
connect[vbcol=seagreen]
> { 
> but 
the[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]

Here it is for APACHEDFT:


# Apache Default server configuration

# General setup directives
HotBackup Off
CgiConvMode %%MIXED/MIXED%%
TimeOut 30000
KeepAlive Off
DocumentRoot /www/apachedft/htdocs
AddLanguage en .en

# Deny most requests for any file
DirectoryIndex index.html
UserDir Disable
<Directory /www/apachedft/htdocs>
order allow,deny
allow from all
</Directory>
<Directory />
order allow,deny
deny from all
Options -Indexes -ExecCGI -includes
AllowOverride Limit Options
</Directory>

# Allow requests for files in document root
Listen 190.190.1.11:80
Options -Indexes
AccessFileName .htaccess

 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


"Sunit Patke" <supatke@nospam.com> wrote in message
news:c6mcs4$oq4$1@news.boulder.ibm.com...
> Is it possible for you to post your httpd.conf file?
>
> Sunit
>
> "C G" <c.g@farmersdairy.ns.ca> wrote in message
> news:c6m8rc$66no$1@news.boulder.ibm.com... 
As[vbcol=seagreen] 
> again. 
> and 
server,[vbcol=seagreen] 
APACHEDFT[vbcol=seagreen] 
> web 
HTTP[vbcol=seagreen] 
HTTP[vbcol=seagreen] 
We[vbcol=seagreen] 
server.[vbcol=seagreen] 
I[vbcol=seagreen] 
> browser 
> connect 
old[vbcol=seagreen] 
deleted,[vbcol=seagreen] 
> the 
>
>

[ Post a follow-up to this message ]

This part in httpd.conf
# Allow requests for files in document root
Listen 190.190.1.11:80
Options -Indexes
AccessFileName .htaccess

making this server listen on port 80

I am guessing that the redirect might be in a META tag in the index.html
page. Check index.html file in /www/apachedft/htdocs subdirectory.

One option to verify this is to change the Listen directive to say port 82.
Then connect to http://<ip address>:82 and see what happens.

Sunit


"C G" <c.g@farmersdairy.ns.ca> wrote in message
news:c6oer4$6sd6$1@news.boulder.ibm.com...
> Here it is for APACHEDFT:
>
>
> # Apache Default server configuration
>
> # General setup directives
> HotBackup Off
> CgiConvMode %%MIXED/MIXED%%
> TimeOut 30000
> KeepAlive Off
> DocumentRoot /www/apachedft/htdocs
> AddLanguage en .en
>
> # Deny most requests for any file
> DirectoryIndex index.html
> UserDir Disable
> <Directory /www/apachedft/htdocs>
>   order allow,deny
>   allow from all
> </Directory>
> <Directory />
>   order allow,deny
>   deny from all
>   Options -Indexes -ExecCGI -includes
>   AllowOverride Limit Options
> </Directory>
>
> # Allow requests for files in document root
> Listen 190.190.1.11:80
> Options -Indexes
> AccessFileName .htaccess
>
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

>
> "Sunit Patke" <supatke@nospam.com> wrote in message
> news:c6mcs4$oq4$1@news.boulder.ibm.com... 
> As 
too[vbcol=seagreen] 
> server, 
> APACHEDFT 
a[vbcol=seagreen] 
> HTTP 
> HTTP 
> We 
> server. 
HTTP[vbcol=seagreen] 
test[vbcol=seagreen]
> I 
> old 
> deleted, 
point[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]

Sorry, maybe I wasn't clear enough.  The index.html file I am trying to
use is the default one that comes with the Apache HTTP Server.  I've used
all the default set up's for the Apache server, just to get it running.  The
only configuation I changed, initially, was for it to listen on port 8022.

Up until two days ago the iSeries was running the old HTTP server (
listening for browser requests on port 80 ) had a custom index.html file
that would redirect the browser to another HTTP server.  When I configured
the Apache server I could only see two servers running in the Administrator
screen:  ADMIN & APACHEDFT.   If I did a WRKACTJOB under QHTTPSVR I would
see both of these also.  If I configured the Apache server to listen on port
8022, I would get the default web page in the browser if I pointed to
http://xxx.xxx.xxx.xxx:8022.   If I went to http://xxx.xxx.xxx.xxx:80 I
would get a page not found message in the browser.  I then went back and
changed the APACHEDFT server to listen on port 80, from port 8022.  When I
did this and went to http://xxx.xxx.xxx.xxx:80 I would get the old
index.html page and it would redirect me to the old server.   The old
index.html page doesn't exist anymore, because I deleted it and the folder
it was in on the IFS after I configured the Apache server.   The only thing
I can think of, that I did wrong, was that I deleted the folder ( and file )
while the old HTTP server was active.




"Sunit Patke" <supatke@nospam.com> wrote in message
news:c6ohep$38r4$1@news.boulder.ibm.com...
> This part in httpd.conf
> # Allow requests for files in document root
> Listen 190.190.1.11:80
> Options -Indexes
> AccessFileName .htaccess
>
> making this server listen on port 80
>
> I am guessing that the redirect might be in a META tag in the index.html
> page. Check index.html file in /www/apachedft/htdocs subdirectory.
>
> One option to verify this is to change the Listen directive to say port
82.
> Then connect to http://<ip address>:82 and see what happens.
>
> Sunit
>
>
> "C G" <c.g@farmersdairy.ns.ca> wrote in message
> news:c6oer4$6sd6$1@news.boulder.ibm.com... 
work.[vbcol=seagreen] 
redirect[vbcol=seagreen] 
> too 
If[vbcol=seagreen]
> a 
our[vbcol=seagreen] 
the[vbcol=seagreen] 
the[vbcol=seagreen] 
Page.[vbcol=seagreen] 
> HTTP 
> test 
the[vbcol=seagreen] 
so[vbcol=seagreen] 
> point 
>
>

[ Post a follow-up to this message ]

CG

I am intrigued.

When you get the port 80 redirect, there should an entry logged in the
access_log of your APACHEDFT server. Can you post it here. It should show
your source (PC) ip address and a get request on /index.html and return code
if there was a redirect etc.

Sunit

"C G" <c.g@farmersdairy.ns.ca> wrote in message
news:c6os2l$69gk$1@news.boulder.ibm.com...
>     Sorry, maybe I wasn't clear enough.  The index.html file I am trying
to
> use is the default one that comes with the Apache HTTP Server.  I've used
> all the default set up's for the Apache server, just to get it running.
The
> only configuation I changed, initially, was for it to listen on port 8022.
>
>     Up until two days ago the iSeries was running the old HTTP server (
> listening for browser requests on port 80 ) had a custom index.html file
> that would redirect the browser to another HTTP server.  When I configured
> the Apache server I could only see two servers running in the
Administrator
> screen:  ADMIN & APACHEDFT.   If I did a WRKACTJOB under QHTTPSVR I would
> see both of these also.  If I configured the Apache server to listen on
port
> 8022, I would get the default web page in the browser if I pointed to
> http://xxx.xxx.xxx.xxx:8022.   If I went to http://xxx.xxx.xxx.xxx:80 I
> would get a page not found message in the browser.  I then went back and
> changed the APACHEDFT server to listen on port 80, from port 8022.  When I
> did this and went to http://xxx.xxx.xxx.xxx:80 I would get the old
> index.html page and it would redirect me to the old server.   The old
> index.html page doesn't exist anymore, because I deleted it and the folder
> it was in on the IFS after I configured the Apache server.   The only
thing
> I can think of, that I did wrong, was that I deleted the folder ( and
file )
> while the old HTTP server was active.
>
>
>
>
> "Sunit Patke" <supatke@nospam.com> wrote in message
> news:c6ohep$38r4$1@news.boulder.ibm.com... 
> 82. 
> work. 
> redirect 
down[vbcol=seagreen] 
ipaddress:80.[vbcol=seagreen]
> If 
> our 
> the 
> the 
> Page. 
a[vbcol=seagreen] 
web[vbcol=seagreen] 
and[vbcol=seagreen] 
> the 
back[vbcol=seagreen]
> so 
>
>

[ Post a follow-up to this message ]

I was intrigued, but now I'm completely stumped.  You'll see what I mean
when you read through this and then look at the log file.

I wasn't using an access_log file, so I created it and tried the following
test.   I set up the Apache server to listen on port 8022.  The web browser,
when specifically pointing to {ip_address:8022}, took me to the default
Apache server index.html, which is what I expected.  If I keyed in
{ip_address:80} I would get a "Page not found" ( or something similar )
.
When I reconfigured the Apache server to listen on port 80, I restarted the
server and keyed in {ip_address:80} in to the web browser.  I got the
redirection index.html and it redirected me to the other HTTP server running
on a NetWare box.  If I keyed in {ip_address:8022} I'd get the "Page no
t
found" message again.

The access_log file is in the following format:

Time
Remote Host
Remote IP
Server Name
File Name
Local IP
First Line of Request
Last Status

The first line is the first test I performed when connecting to port 8022.
The second line is what I got when I changed the listening port to 80.  This
is where I get stumped.  I hope you see something I don't.

[29/Apr/2004:12:31:19 +0000], 190.190.1.201, 190.190.1.201, 127.0.0.1,
/www/apachedft/htdocs/index.html, 190.190.1.11, /index.html, GET / HTTP/1.1,
304
[29/Apr/2004:12:31:57 +0000], 190.190.1.201, 190.190.1.201, 127.0.0.1,
/www/apachedft/htdocs/index.html, 190.190.1.11, /index.html, GET / HTTP/1.1,
304

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


"Sunit Patke" <supatke@nospam.com> wrote in message
news:c6p0cv$66ks$1@news.boulder.ibm.com...
> CG
>
> I am intrigued.
>
> When you get the port 80 redirect, there should an entry logged in the
> access_log of your APACHEDFT server. Can you post it here. It should show
> your source (PC) ip address and a get request on /index.html and return
code
> if there was a redirect etc.
>
> Sunit
>
> "C G" <c.g@farmersdairy.ns.ca> wrote in message
> news:c6os2l$69gk$1@news.boulder.ibm.com... 
> to 
used[vbcol=seagreen] 
> The 
8022.[vbcol=seagreen] 
configured[vbcol=seagreen] 
> Administrator 
would[vbcol=seagreen] 
> port 
I[vbcol=seagreen] 
folder[vbcol=seagreen] 
> thing 
> file ) 
index.html[vbcol=seagreen] 
port[vbcol=seagreen] 
> down 
new[vbcol=seagreen] 
80.[vbcol=seagreen] 
> ipaddress:80. 
as[vbcol=seagreen] 
move[vbcol=seagreen] 
on[vbcol=seagreen] 
HTTP[vbcol=seagreen] 
any[vbcol=seagreen] 
as[vbcol=seagreen]
> a 
> web 
> and 
though[vbcol=seagreen] 
> back 
I[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]

CG

Status code 304 means that browser checked its locally cached file with
server and server replied that the file has not expired.

Please clear the local cache from your browser and retry the test.

Also, when you have the server pointed to port 8022 and you try accessing
port 80 you should see a server timeout error (Cannot find server or DNS
Error Internet Explorer). If you get a page not found error, please use a
complete url http://<ip address>:8022 when using non-standard port. This is
because browsers do not know which protocol to use when not using std ports.

Sunit

"C G" <c.g@farmersdairy.ns.ca> wrote in message
news:c6r87t$4iae$1@news.boulder.ibm.com...
> I was intrigued, but now I'm completely stumped.  You'll see what I mean
> when you read through this and then look at the log file.
>
> I wasn't using an access_log file, so I created it and tried the following
> test.   I set up the Apache server to listen on port 8022.  The web
browser,
> when specifically pointing to {ip_address:8022}, took me to the defau
lt
> Apache server index.html, which is what I expected.  If I keyed in
> {ip_address:80} I would get a "Page not found" ( or something similar
 ).
> When I reconfigured the Apache server to listen on port 80, I restarted
the
> server and keyed in {ip_address:80} in to the web browser.  I got the
> redirection index.html and it redirected me to the other HTTP server
running
> on a NetWare box.  If I keyed in {ip_address:8022} I'd get the "Page 
not
> found" message again.
>
> The access_log file is in the following format:
>
> Time
> Remote Host
> Remote IP
> Server Name
> File Name
> Local IP
> First Line of Request
> Last Status
>
> The first line is the first test I performed when connecting to port 8022.
> The second line is what I got when I changed the listening port to 80.
This
> is where I get stumped.  I hope you see something I don't.
>
> [29/Apr/2004:12:31:19 +0000], 190.190.1.201, 190.190.1.201, 127.0.0.1,
> /www/apachedft/htdocs/index.html, 190.190.1.11, /index.html, GET /
HTTP/1.1,
> 304
> [29/Apr/2004:12:31:57 +0000], 190.190.1.201, 190.190.1.201, 127.0.0.1,
> /www/apachedft/htdocs/index.html, 190.190.1.11, /index.html, GET /
HTTP/1.1,
> 304
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> "Sunit Patke" <supatke@nospam.com> wrote in message
> news:c6p0cv$66ks$1@news.boulder.ibm.com... 
show[vbcol=seagreen] 
> code 
trying[vbcol=seagreen] 
> used 
running.[vbcol=seagreen] 
> 8022. 
([vbcol=seagreen] 
file[vbcol=seagreen] 
> configured 
> would 
on[vbcol=seagreen] 
I[vbcol=seagreen] 
and[vbcol=seagreen] 
When[vbcol=seagreen]
> I 
> folder 
> index.html 
> port 
didn't[vbcol=seagreen] 
> new 
box.[vbcol=seagreen] 
> 80. 
> as 
> move 
put[vbcol=seagreen]
> on 
Home[vbcol=seagreen] 
> HTTP 
> any 
> as 
the[vbcol=seagreen] 
80[vbcol=seagreen] 
> though 
been[vbcol=seagreen] 
and[vbcol=seagreen]
> I 
>
>

[ Post a follow-up to this message ]