Opened 2 years ago

Closed 15 months ago

#6755 closed defect (rejected)

Persistent content blocking redirect problem

Reported by: kzar Assignee:
Priority: P2 Milestone:
Module: Platform Keywords: abp2blocklist
Cc: arthur, mjethani, sebastian, CraftyDeano Blocked By:
Blocking: Platform: Safari
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):



easylist+exceptionrules_content_blocker.json from contentblockerlists rev 329a2b195aae.
Safari 11.1, macOS High Sierra 10.13.4.

How to reproduce

  1. Make sure no Safari extensions are installed.
  2. Use the extension builder to create an empty extension.
  3. Add the content blocking list mentioned above to the extension.
  4. Install the extension, wait 10 seconds to ensure the blocking list has started working.
  5. Browse to this URL:;120523018;w;u=ds&sv1=7731725353&sv2=3057794608038003&sv3=2378027502445129959&gclid=EAIaIQobChMI872CoOLQ2wIViVuGCh2IRwM8EAMYAyAAEgJ59PD_BwE;%3f`

Observed behaviour

The WebKitErrorDomain:104 error message is displayed.

Expected behaviour

Safari successfully redirects to via (Ignore the GDPR error.)


  • Although this is essentially the same as #4280, the difference is that whitelisting the domains in question isn't working. The first redirect to the domain is blocked, despite * already being whitelisted.
  • We've also tried whitelisting specifically but it didn't help.
  • Here are the full URLs in question:;120523018;w;u=ds&sv1=7731725353&sv2=3057794608038003&sv3=2378027502445129959&gclid=EAIaIQobChMI872CoOLQ2wIViVuGCh2IRwM8EAMYAyAAEgJ59PD_BwE;%3f
302 ->
307 ->

Change History (3)

comment:1 Changed 2 years ago by kzar

I suspect this is a Safari bug, but I could be wrong. Either way I can't figure out how why this is happening, the fact you've already whitelisted * should have prevented it.

comment:2 Changed 2 years ago by arthur

  • Cc CraftyDeano added

comment:3 Changed 15 months ago by sebastian

  • Resolution set to rejected
  • Status changed from new to closed

I'm closing all issues related to the legacy Safari extension, as it has been discontinued in favor of an App Extension that doesn't share any code with the old extension.

Note: See TracTickets for help on using tickets.