OWAFull stopped working

[thecroutonman]

OWAFull worked great with OWA (from Office365) until yesterday--now it doesn't work. Not sure if Office365 changed or if Chrome OS changed. Is this project still active/

[ajbogh]

Sorry, I don't have Office 365 to work with. This was designed for Exchange 2007/2010, but if you're able to find the problem with 365 you can submit a PR or mention the issue here and I'd be happy to take a look at it.

[thecroutonman]

Thanks! The url from Office365 starts with https://outlook.office.com/owa/, so I expect this to be a problem with any server using owa.
Here are some symptoms--if you tell me how to get better debugging info, I'll get it.
From my Chromebook, I could only use the "light" version of owa, but once I installed the OWAFull extension, I could use the full version, which was great.
A few days ago when I used a bookmark to open what had previously been the full version of owa, I got this error message:
"The server operation timed out. Please try again later."
If I connect to the owa server a different way (not using the bookmark), I get the "light" version again.
I tried spoofing the server using the "user agent switcher" extension, but I got the same error using either "Firefox for Windows" or "MSIE 10" settings.

[ajbogh]

Through some basic searching I found some people having similar issues. The fix for them was to use the internal domain name to access OWA, instead of the external DNS. I'm not sure how your network is configured but you may be able to use the IP address of the server if you don't have an internal DNS name for the site.

If this solution doesn't apply to you, you can clone the OWAFull project and install it as side-loaded extension to Chrome. Then you can modify the code to troubleshoot what's going on and report back.

I'm sorry that I can't help further because I don't have an Office 365 account and apparently Microsoft doesn't make it easy for developers to get free accounts.

[briankrug]

With a few tweaks I was able to get this working on the OWA setup used by my company. I changed the user-agent string to match IE10 instead of IE9 and I match either /owa/ or /OWA/.
Patch file shown below:

<+>UTF-8
===================================================================
--- src/background.js	(revision 19d22f00f2616ba4a0c939321c68f7e063712e89)
+++ src/background.js	(revision a516b13cf229aa3f03df174531c376c154990eee)
@@ -1,13 +1,15 @@
 var requestFilter = {
 	urls: [
-		"https://*/owa/*"
+		"https://*/owa/*",
+		"https://*/OWA/*"
 	]
 };
 
 chrome.webRequest.onBeforeSendHeaders.addListener(function(details) {
 	var headers = details.requestHeaders;
 	var i;
-	var ieUserAgent = "Mozilla/5.0 (MSIE 9.0; Windows NT 6.1; Trident/5.0)";
+	//var ieUserAgent = "Mozilla/5.0 (MSIE 9.0; Windows NT 6.1; Trident/5.0)";
+	var ieUserAgent = "Mozilla/5.0 (MSIE 10.0; Windows NT 6.1; Trident/5.0)";
 	var loggedIn = false;
 	var bkg = chrome.extension.getBackgroundPage();
 
\ No newline at end of file
Index: src/manifest.json
<+>UTF-8
===================================================================
--- src/manifest.json	(revision 19d22f00f2616ba4a0c939321c68f7e063712e89)
+++ src/manifest.json	(revision a516b13cf229aa3f03df174531c376c154990eee)
@@ -3,13 +3,14 @@
 
   "name": "OWAFull",
   "description": "Allows Chrome to use the full version of Outlook Web Access, instead of being stuck in the light version.",
-  "version": "1.0",
+  "version": "1.1",
   "homepage_url": "https://github.com/ajbogh/OWAFull",
   "permissions": [
     "activeTab",
     "webRequest",
     "webRequestBlocking",
-    "https://*/owa/*"
+    "https://*/owa/*",
+    "https://*/OWA/*"
   ],
   "background": {
     "scripts": ["background.js"],
\ No newline at end of file```

[ajbogh]

@briankrug, please create a pull request with your changes and I will review them. It's difficult for me to test this since my current company uses a newer version of OWA which works with Chrome and FX, however I will do my best. Thanks!

[Ali-Adnan]

My company uses OWA 2007, but the extension is no longer working. Any chance you'd be able to make a fix?

[ajbogh]

Hi @Ali-Adnan. I've merged a new user agent string for IE from PR #4. I will attempt to build a new release soon. If you're willing to test it, please download the source code and install it in Chrome manually and let me know if it fixed the problem.

I'd be happy to accept a Pull Request from you if you're able to fix it yourself, however I do not have access to OWA 2007 anymore.