Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 23149 invoked by uid 500); 9 Apr 2003 22:33:30 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 23136 invoked from network); 9 Apr 2003 22:33:29 -0000 Received: from poison.slackinc.com (12.35.245.16) by daedalus.apache.org with SMTP; 9 Apr 2003 22:33:29 -0000 Received: by smtp.slackinc.com with Internet Mail Service (5.5.2656.59) id <2TMH30W7>; Wed, 9 Apr 2003 17:44:03 -0400 Message-ID: <90A3BA28098BD411AD9A0001FA7E50550345615E@smtp.slackinc.com> From: George Gallen To: "'users@httpd.apache.org'" Date: Wed, 9 Apr 2003 17:44:00 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2FEE1.21BB87B0" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: RE: [users@httpd] referencing without using explicit filenames... . ------_=_NextPart_001_01C2FEE1.21BB87B0 Content-Type: text/plain; charset="iso-8859-1" > > > Try accessing the image directly from both the LAN and WAN. > Do not go through the scripts. What do you see? > > View the page source for the page returned from accessing the site > from the LAN and from the WAN. What is different? LAN = picture is displayed, WAN = picture is not displayed > > >> >> I don't think one being an AOL browser using HTTP/1.0 vs the other >> being >> IE using HTTP/1.1 has anything to do with it...but you never know. >> >> I don't think it has anything to do withe extraneous info from the >> referrer. > > What does mmenu1 do? The parameters being passed in are different mmenu1 is just another .html page (Main MENU), It is the value assigned to the , this way I can tell which pages are being accessed, after this page, all accesses is via a .cgi script and then created dynamically, so I use this method to log which "programs" are accessed in the logs. > between what the log shows for LAN access and WAN access. Whether > this is significant depends upon what the parameters are for? The #'s shown is the cursor position over the image when it's clicked... so unless I have the cursor on the exact same spot, these will always be different. > > >> >> actually, no images ever work from the WAN side, all images work on >> the LAN side. >> however, all html/cgi pages work correctly on both sides. I suspect it to be a configuration problem, but have no idea what/where it could possibly be. Thanks anyway. George > ------_=_NextPart_001_01C2FEE1.21BB87B0 Content-Type: text/html; charset="iso-8859-1" RE: [users@httpd] referencing without using explicit filenames... .

>
>
>  Try accessing the image directly from both the LAN and WAN.
>  Do not go through the scripts.  What do you see?
>
>  View the page source for the page returned from accessing the site
>  from the LAN and from the WAN.  What is different?

LAN = picture is displayed, WAN = picture is not displayed
>
>
>>
>> I don't think one being an AOL browser using HTTP/1.0 vs the other
>> being
>> IE using HTTP/1.1 has anything to do with it...but you never know.
>>
>> I don't think it has anything to do withe extraneous info from the
>> referrer.
>
>  What does mmenu1 do?  The parameters being passed in are different

mmenu1 is just another .html page (Main MENU), It is the value assigned
to the <INPUT TYPE="HIDDEN" NAME="PROGRAM" VALUE="mmenu1">, this way I
can tell which pages are being accessed, after this page, all accesses
is via a .cgi script and then created dynamically, so I use this method
to log which "programs" are accessed in the logs.

>  between what the log shows for LAN access and WAN access.  Whether
>  this is significant depends upon what the parameters are for?

The #'s shown is the cursor position over the image when it's clicked...
<INPUT TYPE="IMAGE" ....> so unless I have the cursor on the exact same
spot, these will always be different.

>
>
>>
>> actually, no images ever work from the WAN side, all images work on
>> the LAN side.
>> however, all html/cgi pages work correctly on both sides.

I suspect it to be a configuration problem, but have no idea what/where
it could possibly be.

Thanks anyway.
George


>

------_=_NextPart_001_01C2FEE1.21BB87B0--