Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #19235
| Message-ID | <3115834.VOAWd18DUa@PointedEars.de> (permalink) |
|---|---|
| From | Thomas 'PointedEars' Lahn <PointedEars@web.de> |
| Organization | PointedEars Software (PES) |
| Date | 2013-04-11 22:04 +0200 |
| Subject | Re: Restrict a domain on Email Validation |
| Newsgroups | comp.lang.javascript |
| References | <9e42c475-f0f4-4822-98d4-0291745f3447@googlegroups.com> <7867864.kBbL0iy7tU@PointedEars.de> <kk70s5$rdc$1@news.albasani.net> <2615387.eNcf81pqbo@PointedEars.de> <kk743r$2vr$1@news.albasani.net> |
Stefan Weiss wrote: > On 2013-04-11 21:09, Thomas 'PointedEars' Lahn wrote: >> Stefan Weiss wrote: >>> On 2013-04-11 20:40, Thomas 'PointedEars' Lahn wrote: >>>> >>>> && !/@forbidden\.[^.]+$/.test(…) > ... >>> That pattern won't match "@forbidden.co.uk". >> >> Correct. Use >> >> … >> && !/@forbidden(\.[^.]+)+$/.test(…) >> >> or >> >> … >> && !/@forbidden(\..+?)+$/.test(…) > > Okay, but that also matches "@forbidden.planet.example.com". So? > In conjunction with the OP's original regex, looking for the substring > "@forbidden." would do the same thing. No, (!x && !y) is logically equivalent to !(x || y). > I don't see any simple and correct general solution for this with a > single regular expression, unless we want to enumerate all currently > known top level domains and their associated reserved second level > domains. Which, by the way, is going to be quite a task soon, because > about 2000 new TLDs are expected to be assigned this year. Maybe you are just thinking about a different problem. -- PointedEars Twitter: @PointedEars2 Please do not Cc: me. / Bitte keine Kopien per E-Mail.
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Restrict a domain on Email Validation GarryJones <morack@algonet.se> - 2013-04-11 10:33 -0700
Re: Restrict a domain on Email Validation Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-11 20:40 +0200
Re: Restrict a domain on Email Validation Stefan Weiss <krewecherl@gmail.com> - 2013-04-11 20:53 +0200
Re: Restrict a domain on Email Validation Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-11 21:09 +0200
Re: Restrict a domain on Email Validation Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-11 21:35 +0200
Re: Restrict a domain on Email Validation Stefan Weiss <krewecherl@gmail.com> - 2013-04-11 21:49 +0200
Re: Restrict a domain on Email Validation Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-11 22:04 +0200
Re: Restrict a domain on Email Validation Stefan Weiss <krewecherl@gmail.com> - 2013-04-11 23:25 +0200
Re: Restrict a domain on Email Validation Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-11 23:31 +0200
Re: Restrict a domain on Email Validation Stefan Weiss <krewecherl@gmail.com> - 2013-04-12 00:23 +0200
Re: Restrict a domain on Email Validation Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-12 00:42 +0200
Re: Restrict a domain on Email Validation Stefan Weiss <krewecherl@gmail.com> - 2013-04-13 11:36 +0200
Re: Restrict a domain on Email Validation Scott Sauyet <scott.sauyet@gmail.com> - 2013-04-20 13:30 -0700
Re: Restrict a domain on Email Validation Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-04-12 00:51 +0200
Re: Restrict a domain on Email Validation Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-04-12 19:36 +0100
Re: Restrict a domain on Email Validation "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-04-13 10:40 +0200
csiph-web