Hi,
Richard Eng wrote:
> The reason I blame Apache is because if you visit...
>
> http://74.102.141.248/goodsexnetwork/
>
> ...to which http://www.goodsexnetwork.com/ has been forwarded, you do not
> see the screen flashing.
>
> So, with...
>
> http://www.goodsexnetwork.com/
>
> ...you see screen flashing, and the "View Source" has the FRAMESET and FRAME
> nonsense that Apache inserted.
>
> With...
>
> http://74.102.141.248/goodsexnetwork/
>
> ...you don't see screen flashing, and the "View Source" shows the actual
> HTML for my webpage. No FRAMESET or FRAME stuff.
>
> What am I supposed to deduce from this? I'm certainly not adding the
> FRAMESET/FRAME stuff. Who is?
>
> -----------
>
> As for the proxy location, it does not have to be a publicly accessible
> website. In fact, that's the whole idea behind reverse proxy--to let Apache
> decide where (which server) to route HTTP requests. These servers will
> typically be behind a firewall where the public can't get at them.
>
> Privacy/Legal works because Apache is being used to serve all static files,
> whereas Seaside is just the web application itself providing the dynamic
> user interactions.
>
> The reason www.goodsexnetwork.com is not yet properly mapped in DNS is
> because I'm still in the development phase, not ready for deployment. My
> server at 74.102.141.248 is just a test platform, which BTW is not up all
> the time (because I'm not testing all the time).
>
> Regards,
> Richard
>
>
> -------------------
> Lester Caine wrote:
>
> I don't believe this has anything to do with apache? I think what ever you
> are using to create your site is creating the frames, to allow it to do some
> of the other effects. Seaside seems to be the culprit on my reading of the
> source.
>
> Also as I understand it, the proxy location has to be a real alternative
> site publicly accessible. I get localhost:9090 can not be found when I try
> to follow links to your own other pages. privacy/legal works because it's
> not being mapped to loaclhost:9090
>
> My own website is on a local machine with a fixed IP address, but until I
> had home.lsces.co.uk properly mapped in DNS everybody kept seeing the IP
> address much like you are getting. I think that you should be using
> www.goodsexnetwork.com/ in the proxy so that apache returns that rather than
> the ip address.
>
> I stand to be corrected as I'm still learning myself ;)
On the grounds that an HTTP request for http://www.goodsexnetwork.com/
returns the following:
GET / HTTP/1.0
Host: www.goodsexnetwork.com
HTTP/1.1 200 OK
Connection: close
Date: Wed, 08 Aug 2007 11:39:55 GMT
Server: Microsoft-IIS/6.0
X-AspNet-Version: 1.1.4322
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 265
<FRAMESET ROWS="*" TITLE="goodsexnetwork.com"><FRAME NAME="top"
SRC="http://74.102.141.248/goodsexnetwork/";
TITLE="goodsexnetwork.com"><NOFRAMES><P>Visit <A
HREF="http://74.102.141.248/goodsexnetwork/";>http://74.102.141.248/goodsexnetwork/</A></NOFRAMES></FRAMESET>Connection
closed by foreign host.
Note the 'Server:' header - this is clearly not an Apache issue. You
need to speak to your web host that maintains the 'forwarding' page to
resolve this issue.
Or failing that, just get www.goodsexnetwork.com pointer to your fixed
IP address!
Neil.
--
Neil Hillard neil.hillard@xxxxxxxxxxxxxxxxxx
AgustaWestland http://www.whl.co.uk/
Disclaimer: This message does not necessarily reflect the
views of Westland Helicopters Ltd.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|