Error No Proxy Found For Favicon.ico
Sign in Pricing Blog Support Search GitHub This repository Watch 26 Star 60 Fork 54 phonegap/connect-phonegap Code Issues 28 Pull requests 8 Projects 0 Pulse Graphs New issue Add proxy to support cross-origin requests #51 Closed mwbrooks opened this Issue May 5, 2014 · 23 comments Projects None yet http://www.ibm.com/support/knowledgecenter/SSPREK_9.0.0/com.ibm.isam.doc/wrp_config/task/tsk_handl_favicon.html Labels enhancement Milestone Issues & Improvem... Assignees No one assigned 4 participants PhoneGap member mwbrooks commented May 5, 2014 Problem: The PhoneGap Developer App cannot make cross-origin requests because it is served by connect-phonegap. Source: phonegap/phonegap-app-developer#98 Solution: One potential https://github.com/phonegap/connect-phonegap/issues/51 solution is to allow the connect-phonegap middleware to proxy all external requests. An added bonus is that the only the CLI needs to be updated, rather each each app. mwbrooks added the enhancement label May 5, 2014 mwbrooks added a commit that referenced this issue May 5, 2014 mwbrooks #51 8bbc5fd mwbrooks added a commit that referenced this issue May 5, 2014 mwbrooks http://drupal.stackexchange.com/questions/87160/gateway-timeout-error-from-proxy-server about hiring developers or posting ads with us Drupal Answers Questions Tags Users Badges Unanswered Ask Question _ Drupal Answers is a question and answer site for Drupal developers and administrators. Join them; it only takes a minute: https://bugzilla.mozilla.org/show_bug.cgi?id=260500 Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Gateway timeout error from proxy server up vote 0 down vote favorite I was error no recently developed a drupal site for a client who lives in HongKong. The site worked perfectly (is still functional when I access it) But after deploying it for demo, the client compalained that the site wasnt working and constantly getting a 504 Gateway timeout error. Apparently the client was on a proxy server (and I'm guessing the problem is due to that factor). Does anyone know of such problem?? And, of course, the way to fix it? error no proxy P.S. The site is built on Drupal 7.14 This is a screenshot that the client sent me (The server, while acting as a gateway or a proxy, did not receive a time response from the upstream server it accessed in attempting to complete the request) Update:: On further investigating with the client, He told me that The site first worked fine until he logged in as admin and added content. The timeout error showed when submitting the content form. After the error, no other page of the site would open. The site did function when he tried after waiting for a while (he did not account the time he waited) UPDATE :: ON checking the error log on the server, I found a bunch of "Page not found errors". But the weird thing is it was looking for a 406 page (for unacceptable header). Any idea why?? [Mon Sep 30 16:45:30 2013] [error] [client 110.44.113.254] File does not exist: /home/ekmauka/public_html/404.shtml [Mon Sep 30 16:45:30 2013] [error] [client 110.44.113.254] File does not exist: /home/ekmauka/public_html/favicon.ico [Mon Sep 30 16:45:29 2013] [error] [client 110.44.113.254] File does not exist: /home/ekmauka/public_html/404.shtml [Mon Sep 30 16:45:29 2013] [error] [client 110.44.113.254] File does not exist: /home/ekmauka/public_html/demo [Mon Sep 30 16:31:17 2013] [error] [client 110.44.113.254] File does not exist: /home/ekmauka/public_html/406.shtml, referer: http://ekmauka.com/ekmauka/ [Mon Sep 30 16:20:40 2013] [error] [client 110.44.113.254] File does not exist: /home/ekmauka/public_html/406.shtml, referer: http://ekmauka.com/ekmauka/content/mongol
BMO. For more details see Persona Deprecated. Last Comment Bug260500 - Browser requests favicon.ico on every page view Summary: Browser requests favicon.ico on every page view Status: RESOLVED WORKSFORME Whiteboard: Keywords: Product: Firefox Classification: Client Software Component: Bookmarks & History (show other bugs) Version: unspecified Platform: x86 All Importance: -- major with 19 votes (vote) TargetMilestone: --- Assigned To: Vladimir Vukicevic (BM, do not Cc or Request) QA Contact: TriageOwner: Marco Bonardo [::mak] Mentors: URL: Duplicates: 267323 277922 281265 (view as bug list) Depends on: Blocks: Show dependency tree /graph Reported: 2004-09-20 03:23 PDT by Thomas Rutter Modified: 2015-08-14 01:07 PDT (History) CC List: 24 users (show) andrzejk brodock bugs bugtrap bugzilla1 cesarb charly41434 edward gavin.sharp gllrmrtfld haakon.nessjoen hoovernj kairo lindyboi michaell+bmo minghong mnyromyr mozilla.org n-roeser nivoside patrick.hendriks+bugzilla pavel.penaz rafaelbardal steve Flags: asa: blocking1.8b5- See Also: Crash Signature: (edit) QA Whiteboard: Iteration: --- Points: --- Has Regression Range: --- Has STR: --- Tracking Flags: Attachments Add an attachment (proposed patch, testcase, etc.) Description Thomas Rutter 2004-09-20 03:23:40 PDT User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040911 Firefox/0.10 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040911 Firefox/0.10 Recently Firefox was changed so that by default, it will search for /favicon.ico (in the root web path) on every page request, where a server doesn't have a /favicon.ico file. However, under this new behaviour the number of HTTP transactions is effectively doubled. For instance, every time I go to a new site Firefox will request the current URL as well as favicon.ico, getting a 404 error for favicon.ico. Unfortunately, it appears that this behaviour was implemented for compatibility with sites designed for Microsoft Internet Explorer. Firefox's current implementation of it is over-agressive and ultimately worse than IE's. Firefox sends a request for /favicon.ico file on every page load, rather than just once when the page is bookmarked. In my opinion, if we are going to add features in order to be compatible with sites designed for Microsoft Internet Explorer, then at the very least these features should not be excessively resour