Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Community Information Center
Community Suggestions and Feedback
Mac-Forums Issues Thread
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Ember1205" data-source="post: 1794923" data-attributes="member: 374272"><p>It isn't my ISP: Attempting to send the same exact message, in the same exact way, from each system results in the exact same error. The two ISP's in use are completely different.</p><p></p><p>It isn't the OS: One machine is MacOS X and the other is Windows 10.</p><p></p><p>It does not APPEAR to be the browser: Chrome on both was able to successfully send shorter messages, but failed on the longer ones. Safari on the Mac had issues with the longer message as well, but I did not try sending a shorter one.</p><p></p><p>Since you were able to send a long string of text, then it isn't purely about the message length. Did you have purely text? What about punctuation? Special characters? My longer message had dashes, parens, an ampersand, dollar sign, and more. It also had quotes. I tried removing those special characters and reverting as pure a text message as possible, and it didn't seem to help.</p><p></p><p>While you are operating multiple machines without issue, take care to understand that I'm not citing that as a creator of a problem... The issue seems to be A) generating errors (when my PM sending attempts fail and I get site errors) and then B) complete blocking of the IP Address. After generating the issue on my Mac with Chrome, for example, attempting to connect from Safari on the same machine doesn't result in a working connection. Attempting to connect from other devices on the same local LAN and being address translated to the same public IP results in no ability to connect - further strengthening my stance that the site is hard-blocking a specific IP after deciding that the error rate is too high from that IP.</p><p></p><p>This kind of intelligent packet handling comes from a Web Application Firewall, an Application Delivery Controller, and/or an Intrusion Protection System. Something has been added to the flow of traffic and it's "sticking its nose where it doesn't belong" and affecting users.</p></blockquote><p></p>
[QUOTE="Ember1205, post: 1794923, member: 374272"] It isn't my ISP: Attempting to send the same exact message, in the same exact way, from each system results in the exact same error. The two ISP's in use are completely different. It isn't the OS: One machine is MacOS X and the other is Windows 10. It does not APPEAR to be the browser: Chrome on both was able to successfully send shorter messages, but failed on the longer ones. Safari on the Mac had issues with the longer message as well, but I did not try sending a shorter one. Since you were able to send a long string of text, then it isn't purely about the message length. Did you have purely text? What about punctuation? Special characters? My longer message had dashes, parens, an ampersand, dollar sign, and more. It also had quotes. I tried removing those special characters and reverting as pure a text message as possible, and it didn't seem to help. While you are operating multiple machines without issue, take care to understand that I'm not citing that as a creator of a problem... The issue seems to be A) generating errors (when my PM sending attempts fail and I get site errors) and then B) complete blocking of the IP Address. After generating the issue on my Mac with Chrome, for example, attempting to connect from Safari on the same machine doesn't result in a working connection. Attempting to connect from other devices on the same local LAN and being address translated to the same public IP results in no ability to connect - further strengthening my stance that the site is hard-blocking a specific IP after deciding that the error rate is too high from that IP. This kind of intelligent packet handling comes from a Web Application Firewall, an Application Delivery Controller, and/or an Intrusion Protection System. Something has been added to the flow of traffic and it's "sticking its nose where it doesn't belong" and affecting users. [/QUOTE]
Verification
Post reply
Forums
Community Information Center
Community Suggestions and Feedback
Mac-Forums Issues Thread
Top