Charcla opened a new issue, #16073:
URL: https://github.com/apache/dubbo/issues/16073

   ### Pre-check
   
   - [x] I am sure that all the content I provide is in English.
   
   
   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Apache Dubbo Component
   
   Java SDK (apache/dubbo)
   
   ### Dubbo Version
   
   jdk:21,dubbo version:3.3.5 ,spring.cloud.nacos.version:3.0.3
   
   
   
   
   ### Steps to reproduce this issue
   
   because of the Company audit requirements,my nacos password need contains:@,!
   I cannot use simple password.
   at the beginning,my nacos password contains & character,but dubbo url need 
this password,and & character Affected URL parameter parsing。so I removed &。
   
   classname:ConfigValidationUtils。
   and I find it only logged error, actually has no effect。
   I wanted to know why has this check and Will there be any bugs later if I 
don't change my password?
   
   
   
   
   ### What you expected to happen
   
   if no effects,can remove this log?
   
   ### Anything else
   
   _No response_
   
   ### Do you have a (mini) reproduction demo?
   
   - [ ] Yes, I have a minimal reproduction demo to help resolve this issue 
more effectively!
   
   ### Are you willing to submit a pull request to fix on your own?
   
   - [ ] Yes I am willing to submit a pull request on my own!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to