You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
The URL is accepted and the link is now set to the specified URL.
Software (please complete the following information):
OS: Arch Linux
Browser: Firefox 131.0.3
Volto Version ?
Plone Version ?
Plone REST API Version ?
I currently do not have access to this information, but I also verified it on the demo system. I can provide this information later on if necessary.
Additional context
It works when using percent encoding to mask the second @ sign (e. g. mailto:[email protected]?cc=test2%40example.com, leading me to suspect that the URL parser is incorrectly parsing the second @ sign as the userinfo delimiter and gets confused.
The text was updated successfully, but these errors were encountered:
I saw this thing, this bug would only occur when links starts with mailto: , this is because the volto's email regex check doesn't deals for cc, bcc, multiple receiver, body, subject and so on...
Doing all these checks in regex, is not possible in my opinion, we'll need to allow multiple repitions of email groups at multiple places with a valid order and valid formats.
Or maybe some REGex Chad developer could do this with regex.
One simpler approach would be sort of compromise check for cc and multiple receiver, i.e., allow user to enter mailto:[email protected],{anything} or mailto:[email protected]?cc={anything}. This wont be safe tough.
Describe the bug
Links with two @ signs, like
mailto:[email protected],[email protected]
ormailto:[email protected][email protected]
, are not accepted when entered into the Edit Link field.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The URL is accepted and the link is now set to the specified URL.
Software (please complete the following information):
I currently do not have access to this information, but I also verified it on the demo system. I can provide this information later on if necessary.
Additional context
It works when using percent encoding to mask the second @ sign (e. g.
mailto:[email protected]?cc=test2%40example.com
, leading me to suspect that the URL parser is incorrectly parsing the second @ sign as the userinfo delimiter and gets confused.The text was updated successfully, but these errors were encountered: