[Request for Help] When configuring a custom HTTP SMS (SMSbao) in Casdoor, the verification code variable {code} cannot be replaced.
Problem description:
I am currently configuring a custom HTTP SMS service using Casdoor (leveraging the SMSBao interface). The interface can be successfully called, and SMS messages are sent without issues. However, the received SMS content displays the verification code as the literal string {code}, rather than the dynamically generated numeric verification code.
Environmental information:
Service Type: Custom HTTP SMS
Request method: GET
SMS Service Provider: SMSBao
Current Configuration Details:
Regional Node (Endpoint):
https://api.smsbao.com/sms?u=3400271386&p=******&m={mobile}&c=【Yibingchen Applied Science and Technology Research】Your verification code is {code}. If this is not for your own operation, please ignore this SMS..
Encountered phenomena:
The actual received SMS content was: "【Yibingchen Applied Science and Technology Research】Your verification code is {code}. If this is not your operation, please ignore this message.". ”
Casdoor appears to have sent the verification code as plain text instead of replacing the {code} placeholder in the URL with the actual variable.
Help:
How can the code variable be correctly passed and replaced in Casdoor's custom HTTP SMS? Is special URL encoding required in the endpoint, or are there other requirements for the mapping format of Params?
