Reply to thread

Message

<blockquote data-quote="JasonUK" data-source="post: 925710" data-attributes="member: 86995"><p>Thanks for the replies above... so reason for opening post recommended http://*^$third-party,~image,~stylesheet without any || at all would suggest that in the original opening posters version the http://* was explicitly stating the internal translation of http:// because no | had been used and the ^ was to include sub-domains (quoting Jan Willy&#039;s post #68 second example).&nbsp; If you put a single | in front you can scrap the * making it tighter (Lenny&#039; post #72) but doesn&#039;t that mean you lose the wildcard element which was referred to in post #67?&nbsp; Now I&#039;m totally confused <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />&nbsp; I think I&#039;ll stick to the original until I wrap my brain around the syntax rules!</p></blockquote><p></p>

[QUOTE="JasonUK, post: 925710, member: 86995"] Thanks for the replies above... so reason for opening post recommended http://*^$third-party,~image,~stylesheet without any || at all would suggest that in the original opening posters version the http://* was explicitly stating the internal translation of http:// because no | had been used and the ^ was to include sub-domains (quoting Jan Willy's post #68 second example). If you put a single | in front you can scrap the * making it tighter (Lenny' post #72) but doesn't that mean you lose the wildcard element which was referred to in post #67? Now I'm totally confused :) I think I'll stick to the original until I wrap my brain around the syntax rules! [/QUOTE]

Verification