Re: [users@httpd] Browser differences
Thanks for the prompt response. On 3 May 2017 at 13:55, Ramsey, Robert L <robert-ram...@uiowa.edu> wrote: > This is just my non-apache two cents. > Yes, I realise it might not be an Apache problem. But it did start appearing around the time yum gave us a new version of Apache... > - Is your js loaded after all of the libraries? Are you sure? > Yes. I thought it was, and I just thecked. Following a bunch of CSS files, we have JQUery, Several other third party libraries, including OpenLayers and Backbone JQuery Mobile. Our main (1.7MByte minified) JS file A 500kByte minified compiled templates file. A couple of tiny JS (configuration) files A40KByte "top level" JS file. And THIS, last, file is the one that Chrome says times out! However, I will try re-ordering things, and see if that makes a difference... > - Is your js file one huge file or many little ones? It sounds > like one big file. > Mostly one big one. But that isn't the file that times out! However, I'll try splitting it, too... And it is straight JS. > > You’ve probably already looked at those, but sometimes it helps to have > another person chime in. > | A js/chrome list might be more appropriate too. Maybe. I had two vague ideas, and I wanted to see whether anyone else would suggest them: * The problem is related to a limit on the number of (simultaneous) fetches from a single client, and the new version of Apache has changed that limit, or * Chrome is picking up an ISP's a proxy configuration that FFox is not, and it is the ISP's proxy that is/was causing the problem. Robert. > > > > > *From:* robertin...@gmail.com [mailto:robertin...@gmail.com] *On Behalf > Of *Robert Inder > *Sent:* Wednesday, May 3, 2017 4:34 AM > *To:* users@httpd.apache.org > *Subject:* [users@httpd] Browser differences > > > > We have developed a complex javascript application > > There are "a few megabytes" of our own code, plus OpenLayers map handling > and jQuery. > > > > We're serving it through Apache 2.2.15-59, which arrived on CentOS 6.9 in > mid April. > And everything works well and reliably for us. > > > > But for the last couple of weeks, our client has been experiencing > problems starting the application. > > The Javascript console reports that some Javascript files are not loading > because "Connection Timed Out" on one of the JS files. > > Apache is not logging any errors. > > > The obvious explanation would be in terms of network connection between > him and the hosting company. > But his connection is actually faster than ours > AND he only has problems when he uses Google Chrome: Firefox is fine. > > > So I'm struggling to think what this can be. Any suggestions? > > > Our client started having problems at ABOUT the time that yum installed > 2.2.15-59. > > Has something changed? > > > > Robert > > > -- > > Robert Inder,0131 229 1052 / 07808 > 492 213 <07808%20492213> > Interactive Information Ltd, 3, Lauriston Gardens, Edinburgh EH3 9HH > Registered in Scotland, Company no. SC 150689 >Interactions speak louder than > words > -- Robert Inder,0131 229 1052 / 07808 492 213 <07808%20492213> Interactive Information Ltd, 3, Lauriston Gardens, Edinburgh EH3 9HH Registered in Scotland, Company no. SC 150689 Interactions speak louder than words
RE: [users@httpd] Browser differences
This is just my non-apache two cents. Chrome does a number of things that are . . . interesting, let’s say. Just from my own experience, some things to look for which you probably thought of already, and aren’t apache specific: - Is your js loaded after all of the libraries? Are you sure? I had a similar problem and I had all of my js references at the bottom of the body as you should, with jquery loaded first, 3-5 other libraries in-between, then my js. I moved just jquery and bootstrap to the head and loaded my js file from the bottom of the body. Then the error I had about jquery not being loaded went away. Like yours, it worked in FF but not Chrome. - Is your js file one huge file or many little ones? It sounds like one big file. Maybe break it up to see if loading many smaller files works for this client. One place I worked actually had a css file that was too big for some clients, so splitting it up and loading it in the right order fixed problems. - Is this straight js or are you transpiling jsx/tsx files? Check the config for the transpiler to see if it is doing anything weird. Maybe strip comments out if you really need one big file. You’ve probably already looked at those, but sometimes it helps to have another person chime in. A js/chrome list might be more appropriate too. You are lucky that you are working with one client. I’m doing a small project that needs to be compatible back to IE9, has unsophisticated users, and has users with accessibility requirements beyond straight wcag 2.1 AA. Luckily the user base is < 100,000. bob From: robertin...@gmail.com [mailto:robertin...@gmail.com] On Behalf Of Robert Inder Sent: Wednesday, May 3, 2017 4:34 AM To: users@httpd.apache.org Subject: [users@httpd] Browser differences We have developed a complex javascript application There are "a few megabytes" of our own code, plus OpenLayers map handling and jQuery. We're serving it through Apache 2.2.15-59, which arrived on CentOS 6.9 in mid April. And everything works well and reliably for us. But for the last couple of weeks, our client has been experiencing problems starting the application. The Javascript console reports that some Javascript files are not loading because "Connection Timed Out" on one of the JS files. Apache is not logging any errors. The obvious explanation would be in terms of network connection between him and the hosting company. But his connection is actually faster than ours AND he only has problems when he uses Google Chrome: Firefox is fine. So I'm struggling to think what this can be. Any suggestions? Our client started having problems at ABOUT the time that yum installed 2.2.15-59. Has something changed? Robert -- Robert Inder,0131 229 1052 / 07808 492 213 Interactive Information Ltd, 3, Lauriston Gardens, Edinburgh EH3 9HH Registered in Scotland, Company no. SC 150689 Interactions speak louder than words
[users@httpd] Browser differences
We have developed a complex javascript application There are "a few megabytes" of our own code, plus OpenLayers map handling and jQuery. We're serving it through Apache 2.2.15-59, which arrived on CentOS 6.9 in mid April. And everything works well and reliably for us. But for the last couple of weeks, our client has been experiencing problems starting the application. The Javascript console reports that some Javascript files are not loading because "Connection Timed Out" on one of the JS files. Apache is not logging any errors. The obvious explanation would be in terms of network connection between him and the hosting company. But his connection is actually faster than ours AND he only has problems when he uses Google Chrome: Firefox is fine. So I'm struggling to think what this can be. Any suggestions? Our client started having problems at ABOUT the time that yum installed 2.2.15-59. Has something changed? Robert -- Robert Inder,0131 229 1052 / 07808 492 213 Interactive Information Ltd, 3, Lauriston Gardens, Edinburgh EH3 9HH Registered in Scotland, Company no. SC 150689 Interactions speak louder than words
