I don't think there is a work around. Why do you need to alter the User-Agent header?
Adam On Fri, Jan 8, 2010 at 5:33 PM, Simon <[email protected]> wrote: > k, just read through some posts, i know the reason why. it's because > the extension carried over the restriction from the chrome browser > itself. > However, is there a work around for this? > > On Jan 8, 5:29 pm, Simon <[email protected]> wrote: >> has anyone tried it yet? >> I tried to set a different user agent in my request and it triggered >> "Refused to set unsafe header "User-Agent" >> >> ex: >> req.setRequestHeader("User-Agent", "Mozilla/5.0 (Windows; U; Windows >> NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1"); >> >> anyone know why and how to get around this? > > -- > You received this message because you are subscribed to the Google Groups > "Chromium-extensions" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > > > >
-- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
