What regex URL can be used in the Allowed Origins?
# support
v
@kietnguyen I'm here to help! It looks like you're trying to use a regular expression for a URL validation, but there seems to be a small mistake in the pattern you provided. The correct regular expression pattern for matching a URL might look something like this:
https://.+\.example\.com
. Make sure to escape the dots with a backslash to ensure they are treated as literal dots, not as wildcard characters. If you're implementing this in a form and it's still not accepting valid URLs, there might be an issue with how the form is processing the regular expression. If you need further assistance with this, could you please provide more details about where you're trying to use this regular expression?
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
can someone in @User help with this question?
s
@kietnguyen The input https://.+.example.com/ will fail because the hostname .+.example.com is not valid. The function checks for URLs with a wildcard by determining if the hostname starts with *.
.+
doesn't match the criteria, and regular expression used for validation will also fail since .+ is not a valid hostname according to URL standards.
Valid Example:
https://*.example.com/
k
I've tried
https://*.example.com
and
https://*.example.com/
and it did not work
can you take a look to see if this is a bug?
k
I meant it worked to setup the public key, but it's not work when I start vapi call. I got the cors error
s
@kietnguyen can you record a loom video when you try to make the web call, and show the CORS in console logs and n/w tab your getting and the payload used for making the call!!
2 Views