Posted by xxm on December 19, 2008 at 3:50pm
| Project: | Whois lookup |
| Version: | 6.x-1.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Only when ajax is enabled somtime the error "Error requesting data!" errises. I suppose, the timeout is to short but I don't know how to change ist. Where an how do can we change the timeout time?
Comments
#1
Any updates on this error? - I can say as much as it for me only happens on .com TLD's when using a - in the domain like kazi-networks.com. But still not on .DK TLD's.
#2
If the lookup contains a hyphen, no result is returned.
With ajax turned on, there is an "Error requesting data!" message that pops up in the top right corner. With ajax turned off there is no error returned. Either way, no result is returned, so I don't think it is an ajax issue.
I upped this to critical.
#3
I have this problem as well. When Ajax and Basic or HTML are selected it sometimes gives an error. Never give this error when Ajax is deselected.
#4
Just checking to see if there is a fix for this yet. I've gone through and removed the module, re-added it, messed around with the library, still returns "Error Requesting Data!". I guess I'll have to remove it again until there's a fix. That's a shame, it was really useful when trying to figure out who was hitting my website from where in case I needed to block them.
#5
A dash '-' in the domain name is currently a certain reason for failure due to the way whois_parse_url() filters POST requests.
The attached patch fixes this issue with the filtering regexp, this however needs more work.
#303833: Fix the url regular expression is related to this issue.
For other cases the error handling vs. ajax support has to be improved, not sure when I have time for that.
#6
Fix for #653156: Unfixable whois_parse_url, which should resolve the whois_parse_url() issue, has been committed.
The code in whois.js sets a timeout of 5 seconds on line 104. Due to the reliance on external services I will up this to 10 sec.
Please re-open this issue if the problem persists.
#7
Automatically closed -- issue fixed for 2 weeks with no activity.