[email protected] parsed as 2 urls

[ddosoff]

[email protected] parsed as:

1. http://name.lastname/
2. http://gmail.com/

[davidthemarsh]

I am also seeing this - are there plans to fix it?

[kodjobaah]

seeing the same problem as @davidthemarsh.

[worpet]

I am impacted by this also. Dot containing emails are much more common than I had realized.

[tzuhanjan]

Hmm this is a greedy evaluator, so it matches whatever completes a url first. What should be the correct behavior in this case in your opinions? Should it be one url as [email protected] with an identifier saying that the URL is an email?

[worpet]

@tzuhanjan: Expected behavior for me would be "[email protected]" is detected as a single Url with host gmail.com and username name.lastname.

[capnbab]

@tzuhanjan Also having this issue. I agree with @worpet, it would be ideal if "[email protected]" was detected as a URL with host gmail.com and username name.lastname. For my use case, I need to exclude hits that look like pure e-mail addresses. So after detecting, I only include where url.getUsername().isEmpty(). This breaks for me on any e-mail address with a dot in the local part.