Open jbuckner opened 10 years ago
This is interesting.
The favicon.ico file is also 404ing according to those logs, but it is definitely there.
Ping @kahnjw
adrian@yoshi:~$ curl -v http://sitebuilder.yola.com/favicon.ico > /dev/null
* Trying 208.75.209.79...
* Connected to sitebuilder.yola.com (208.75.209.79) port 80 (#0)
> GET /favicon.ico HTTP/1.1
> User-Agent: curl/7.30.0
> Host: sitebuilder.yola.com
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Date: Wed, 23 Jul 2014 06:51:29 GMT
* Server Apache is not blacklisted
< Server: Apache
< Last-Modified: Tue, 22 Jul 2014 21:58:10 GMT
< ETag: "2d617ce-2c0-4fecf51c2aad5"
< Accept-Ranges: bytes
< Content-Length: 704
< Vary: Accept-Encoding
< Yola-ID: sb1 D=398 t=1406098289523004
< Content-Type: text/html
Ah, sitebuilder, I thought I was looking at yolacom logs.
This is a bit of a bizarre issue brought up by Jen in CS:
If a user puts a link to SiteBuilder in an Excel document (it could happen in other Office apps, but haven't verified), we send them to the "Browser Unsupported" page even if it is opening in Chrome or Firefox. I was doing a bit of digging and for some reason, the initial request to SiteBuilder after the user has clicked the link, identifies itself as IE7, even though the website is being opened in Chrome or Firefox.
It looks like there's some discovery happening at first. Look at the end of the user agent. It has
ms-office
in it.Here's the Apache logs from a click from Excel:
Opening in Chrome from Excel:
Opening in Firefox from Excel: