Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parser assumes that characters have been encoded in a post when HTML is enabled #4727

Open
Sama34 opened this issue Jun 9, 2023 · 0 comments
Labels
b:1.8 Branch: 1.8.x p:medium Priority: Medium. Issues to be resolved with normal preference t:bug Type: Bug. An issue causing error / flaw / malfunction

Comments

@Sama34
Copy link
Contributor

Sama34 commented Jun 9, 2023

The following line assumes that characters have been encoded :

(?:/(?:[^\"\s<\[&]|\[\]|&(?:amp|lt|gt);)*)? # path, query, fragment; exclude unencoded characters

Which is untrue when HTML is enabled.

Reference :
https://community.mybb.com/thread-237311-post-1382420.html#pid1382420

@Sama34 Sama34 added t:bug Type: Bug. An issue causing error / flaw / malfunction b:1.8 Branch: 1.8.x p:medium Priority: Medium. Issues to be resolved with normal preference labels Jun 9, 2023
@Sama34 Sama34 changed the title URL incomplete link in a post Parser assumes that characters have been encoded in a post when HTML is enabled Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
b:1.8 Branch: 1.8.x p:medium Priority: Medium. Issues to be resolved with normal preference t:bug Type: Bug. An issue causing error / flaw / malfunction
Projects
None yet
Development

No branches or pull requests

1 participant