Hi @taehoon ham ,
Based on the configuration you provided, it looks like you are using Enterprise Mode .v2 Schema. But it's not configured correctly as documented, and I think that's what caused this issue:
We recommend that you not add any of the following items to your schema because they can make your compatibility list behave in unexpected ways:
- Don’t use protocols. For example,
https://, or custom protocols. They break parsing.
- Don’t use wildcards.
- Don’t use query strings, ampersands break parsing.
Please try removing
https:// from the configuration, I think this will work for you. You can also refer to this document for more details: Enterprise Mode v.2 schema example.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.