Forum: Ruby on Rails Duplicate requests

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
807e34b31d5463a9ac05d41458a9e537?d=identicon&s=25 Al Evans (al-evans)
on 2007-02-18 16:36
Can someone point me toward an explanation of what's happening here?
Apache 2.2, proxy_cluster, mongrel. Here's the production.log output
from a single request:

Processing ThingsController#index (for 208.188.101.145 at 2007-02-18
07:31:06) [GET]
  Session ID: b1fc68b0aee9f141187d4a04bf54daa3
  Parameters: {"action"=>"index", "controller"=>"things"}
Rendering  within layouts/application
Rendering stories/index
Completed in 0.00506 (197 reqs/sec) | Rendering: 0.00391 (77%) | DB:
0.00034 (6%) | 200 OK [http://storysquared.com/]


Processing ThingsController#index (for ::1 at 2007-02-18 07:31:11) [GET]
  Session ID: 0c48b261a9ecd2b6f88b002210168834
  Parameters: {"action"=>"index", "controller"=>"things"}
Rendering  within layouts/application
Rendering stories/index
Completed in 0.00564 (177 reqs/sec) | Rendering: 0.00461 (81%) | DB:
0.00032 (5%) | 200 OK [http://127.0.0.1/]


Where is the second request coming from (bad Apache config?), and what
does the ::1 mean?

Thanks!

--Al Evans
8589dbd737a28d39bb1dcd5251262e3b?d=identicon&s=25 Oyku Gencay (Guest)
on 2007-02-18 16:49
(Received via mailing list)
Hi,

::1 is an IPv6 address. Please check your network configuration.
Without looking any further I can tell that you should focus on which
IP address your daemons are listening to.
Hope this helps.

Regards,
Oyku.
807e34b31d5463a9ac05d41458a9e537?d=identicon&s=25 Al Evans (al-evans)
on 2007-02-18 19:12
Oyku Gencay wrote:
> Hi,
>
> ::1 is an IPv6 address. Please check your network configuration.
> Without looking any further I can tell that you should focus on which
> IP address your daemons are listening to.
> Hope this helps.
>
> Regards,
> Oyku.

Thanks! They're listening on 127.0.0.1, on a couple of groups of ports,
so that makes sense (I'm not used to IPv6).

As it happens, I fixed the problem shortly after posting here. For some
reason, I had forgotten to remove an outdated set of ProxyPass,
ProxyPassReverse, and ProxyPreserveHost directives for a different
vhost. I have no idea why they would have caused this problem, but
taking them out fixed it.

--Al Evans--
This topic is locked and can not be replied to.