Loading Profile...
Spike is unable to handle IP addresses that start with '120'
The following entry in a Rails log causes Spike to freeze while processing the log. I narrowed the problem down to the IP address. After changing the first number of the address, '120', to something else Spike was able to process it successfully. I am using Spike 1.1.0.
Processing PostsController#index (for 120.28.222.79 at 2009-07-10 06:54:10) [GET]
Parameters: {"embed_300"=>"1", "embed_key"=>"6890314e56", "action"=>"index", "parent_url"=>"http://example.com/foo", "controller"=>"posts"}
Rendering template within layouts/widget_small
Rendering posts/widget_300
Completed in 11ms (View: 2, DB: 1) | 200 OK [http://www.example.com/embed_300?pare...]
Processing PostsController#index (for 120.28.222.79 at 2009-07-10 06:54:10) [GET]
Parameters: {"embed_300"=>"1", "embed_key"=>"6890314e56", "action"=>"index", "parent_url"=>"http://example.com/foo", "controller"=>"posts"}
Rendering template within layouts/widget_small
Rendering posts/widget_300
Completed in 11ms (View: 2, DB: 1) | 200 OK [http://www.example.com/embed_300?pare...]
I’m confused
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Thank you for the report.
I can confirm that with 120 it never finishes processing but with 119 or 121 it does. Puzzle!
I'm using the Cocoa function 'hostWithAddress' to parse the IP address and it seems pretty unlikely that there's going to be such a serious problem there.
At the same time, I can't see how 120 rather then 119 or 121 makes any difference to the code ripping out the IP.
Unfortunately, at the moment, I do not have time to look any more deeply into the problem. But if & when I do I will post an update.
Regards,
Matt
EMPLOYEE
