Akram K.
08/16/2024, 3:12 PMVapi
08/16/2024, 3:13 PMexample.com
using HTTPS:
^https:\/\/(?:.*\.)?example\.com$
This regex breaks down as follows:
- ^
asserts the start of the line.
- https:\/\/
matches the https://
part of the URL.
- (?:.*\.)?
is a non-capturing group that matches any characters followed by a dot (.
), and it's optional because of the ?
.
- example\.com
matches the domain example.com
(the backslash escapes the dot to match it literally).
- $
asserts the end of the line.
Make sure to test your regex with the URLs you expect to allow to ensure it works as intended. If you need further assistance with regex patterns or have other questions, feel free to ask!Vapi
08/16/2024, 3:13 PMVapi
08/16/2024, 3:15 PMAkram K.
08/16/2024, 3:15 PMSahil
08/17/2024, 11:29 AMAkram K.
08/17/2024, 5:08 PMSahil
08/17/2024, 6:24 PMSahil
08/17/2024, 6:24 PMSahil
08/17/2024, 6:24 PMAkram K.
08/18/2024, 8:46 AMVapi
09/23/2024, 9:32 PMVapi
09/23/2024, 9:33 PMhttps://site34453.weebly.com/
. Here's a regex pattern that should work:
^https:\/\/site34453\.weebly\.com\/?$
This regex will match the URL starting with https://
, followed by your specific subdomain and domain, and allows for an optional trailing slash at the end. The backslashes (\
) are used to escape special characters like .
to ensure they are treated as literal periods in the URL.
Please try using this regex pattern and see if it is accepted. If you encounter any further issues, let me know, and I'll be happy to assist you further.Vapi
09/23/2024, 9:33 PM^https:\/\/site34453\.weebly\.com\/?$
This regex ensures that the URL starts with https://
, followed by your exact subdomain and domain, and optionally ends with a forward slash.
If this still doesn't work, it might be best to consult the documentation of the system you're using to see if there are any specific guidelines for the regex patterns, or reach out to their support team for assistance.
If you need further help or have any other questions, please let me know.