search : ipv6

[ANeff] Doc Bug for: isIPv6() missing parameters

Bug 87138:-(Watson Migration Closure) IsValid("url", ...) and IsValid("email", ...) do not correctly validate values that use IPv6-based addresses

2609134 CF-3924581 Immanuel N. Aaron, regarding the ipv6 support, I can confirm this is fixed and will be available in a future release.

4754893 CF-4203295 Charlie A. Here is the blog post I did on this, posted just after filing this bug: https://www.carehart.org/blog/client/index.cfm/2018/8/24/fixing_CF_debugging_output_for_ipv6_localhost#more

4444758 CF-4202804 Language : Functions [ANeff] Bug for: CF-3044064 hidden Issue: CF-3044064 hidden CF-3044064 was fixed in CF11 Update 5 but is hidden in the tracker. CF11 Update 5's description is: "IsValid("url", ...) and IsValid("email", ...) do not correctly validate values that use IPv6

Migration Closure) IsValid("url", ...) and IsValid("email", ...) do not correctly validate values that use ... ----------- It's just about IPv6 support in isValid(). Must it remain secretive? Thanks!, -Aaron

2609134 CF-3924581 Milan C. as reported 'http://[::1]' was already fixed with ipv6 support. support for these spcl characters: ! ( ) and * is added. behavior of % will remain as it is. We will not make it stricter by validating only when it is followed by 2 hexadecimal characters. Though

2609134 CF-3924581 External U. Hi Milan, "as reported 'http://[::1]' was already fixed with ipv6 support." As reported? Where? isValid("url", "http://[::1]") returns NO in CF11 Update 3 and CF11 Update 4. "w3c spec as it should be used strictly" Strictly is the only way in which Adobe should

2613554 CF-3231157 Adobe D. Fixed: Here are some more email ID's tested with their result using isValid() : "()[]:,;@\\\"!#$%&'*+-/=?^_`{}| ~.a"@example.org: YES " "@example.org: YES admin@mailserver1: YES user@[IPv6:2001:db8:1ff::a0b:dbd0]: YES "very.(),:;[]\".VERY.\"very@\\ \"very

4754893 CF-4203295 Administrator CF Admin does not accept ::1 for "debugging ip addresses", so localhost debugging fails for many Problem Description: For those who enable CF debug output but are on OSs using ipv6, when they use "localhost" as the url for testing, they find that don't see

.xml as the "address" attribute), for indicating what IP address should be allowed for requests into the connector from wherever the web server is. Even if one thinks "my web server is on the same machine as CF, so it should be 127.0.0.1", the problem is that if your machine supports both ipv4 and ipv6, it won