-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CTCP PING does not return correct value #519
Comments
Can you be more specific? What is the exact problem? And, if multiple IRC clients have the same problem, what would you like Indy to do about it? Sounds like maybe it is a server-side problem. |
Sorry for not being specific. When running an irc client under IdIRC.pas, I would use a different irc client such as mIRC to ping the id irc client, but it returns weird values such as PING REPLY 47367hrs 30mins 54secs. It doesn’t make sense for a ping reply to take that long. I have tested with different irc clients and all gave the correct response except for IdIRC. You can test it by running a connection to any irc server using IdIRC, and then use a different irc client to ping it. |
I think the problem stems from Try this - in
To this instead:
If that works, I will merge it in. |
I tried the change but it doesn’t seems to work, or I am doing it wrongly. I changed the source directly from the folder and saved it and run my project but it doesn’t seems to reflect the changes. |
Are you compiling Indy's source files directly into your project? If not, then you have to recompile+reinstall the Indy libs and link them into your project. |
Any update? |
…NG using the sender's data that was received. Bumping version number. Adding some TODO comments.
Hello,
When receiving a CTCP ping on the irc client, it returns a value that is very far off than what seems correct.
I thought it was an error, and have tested with multiple irc clients and all leading to the same result.
Thanks.
The text was updated successfully, but these errors were encountered: