Change the User-Agent

Bug #1098151 reported by psypher on 2013-01-10
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

When using Fogger to connect to Outlook Web Access, it defaults to the lite version. All that is need to connect to the premium Outlook Web Access Client is to trick the browser into using a different user agent. This can be done with Chrome like so:
/opt/google/chrome/google-chrome --user-agent="Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US) AppleWebKit/534.4 (KHTML, like Gecko) Chrome/6.0.481.0 Safari/534.4"

Is there any way we can integrate this kind of feature into fogger? Perhaps an option in the App preferences to pass parameters to webkitgtk? Would webkitgtk be able to do this?

If this is possible via an option in preferences, could there be a temporary workaround hack that can get this done in the meantime?

Alba Mendez (jmendeth) wrote :

If the service is HTTP (not HTTPS) then there is
indeed a temporal workaround/hack, and it is to use a proxy
to fake the User Agent.

Alba Mendez (jmendeth) on 2013-01-10
summary: - Outlook Web Access Premium
+ Change the User-Agent

Unfortunately HTTPS

On Thu, Jan 10, 2013 at 4:35 PM, Xavier Mendez <email address hidden> wrote:

> If the service is HTTP (not HTTPS) then there is
> indeed a temporal workaround/hack, and it is to use a proxy
> to fake the User Agent.
> --
> You received this bug notification because you are subscribed to the bug
> report.
> Title:
> Outlook Web Access Premium
> To manage notifications about this bug go to:

If you are looking for something that will expand your mind, open your
heart, and possibly rekindle your faith in humankind, a good place to start
is listening to the fabulously inspiring presentations made by the best and
brightest among us.

Go visit: and watch some TED Talks. Ideas Worth Spreading :)

Kevin (kupiakos) wrote :

I have the exact same problem you have with the Outlook Web App. After analyzing the code, here are instructions for a workaround:

Navigate to /opt/
Open fogger/ for editing as root.
Insert the following line after Line 152 (on mine, it is self.websettings.props.enable_plugins = True):
self.websettings.props.user_agent = 'Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0'
(make sure to insert spaces so it matches the line above)
Save and close the file.

You may not have to do these next few steps, but for some reason it fixed a hanging problem I had:
Open fogger_lib/ for editing as root.
Add # to the beginning of line 94 to turn this line:
into this:
Save and close the file.
I'm not sure what negative affect this has on the webapp (I'm not exactly a PyGtk guru here)

I should probably put this as a patch, but I'm a little rusty with diff and I don't want to break anything. Hopefully this solves your problem for now. Also keep in mind this useragent and other settings will be applied for *all* webapps.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers