Placing "run_at":"document_start"
causes non of the URL's to run the content script, even those that worked without the redirect shown above. On Nov 4, 2:13 pm, Aaron Boodman <a...@chromium.org> wrote: > Seems like a bug. Did you try a few different settings for run_at ? > Do they all have the same problem? > > - a > > > > On Wed, Nov 4, 2009 at 10:47 AM, jfc <jfceklo...@gmail.com> wrote: > > > I am trying to use a content script with the following mask: > > > http://*.foo.com/* > > > The pages fromhttp://test.foo.com/whateverwork fine, but when I have > > something like the following: > > > Get onhttp://test.foo.com/hello > > which does a redirect (HTTP 302) tohttp://check.foo.com/check > > (returns HTTP 401), then a get onhttp://check.foo.com/check, and > > finally a redirect (return HTTP 302) back tohttp://test.foo.com/hello > > > The content script never executes. > > > Any thoughts here? The above examples deals with a single sign on > > product.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensions@googlegroups.com To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
