-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generating two page requests #1
Comments
The extension relies on being able to get the raw, original HTML in On 5/31/2013 11:25 AM, Bjoern wrote:
|
Ok. The red button on the right handside makes Chrome put two of that kind into my shopping cart. |
I know this is an old issue, but this is happening for me. I'm a web developer, and I can definitely see two requests hitting my development server while I have Spof-o-matic enabled. |
Do you see 2 POST's or just double GET's? The double GETs are expected because that's the only way for the extension to get the original HTML (sadly the extension API doesn't provide access to the response body for requests). |
I believe it's just GETs. So you can't do the analysis on the DOM and you need the original HTML string? That's a shame. Spof-o-matic is useful, but it looks like I'll have to enable it only when I specifically need to use it. At least this has solved a mystery for me; I really couldn't understand why my server debugger was running twice each time I refreshed Chrome. |
Correct. The DOM includes script tags that were dynamically injected which are non-blocking and SPOF-O-Matic needs to be able to detect parsed (blocking) tags from the original HTML. |
Hey,
When having your plugin running in Chrome, it doubles the number of document requests (proven in Fiddler2)-
This leads for example to placing the doubled amount of stuff in the shopping cart .
Or my online banking refuses some actions because Chrome fires 2 Document Requests per Pageload .
I tried to fork & fix this but my experience in Chrome extension is only slightly above zero.
My suggestion would be to use a contentscript to fish the document.innerHTML rather than doing an additional request.
Cheers
Bjoern
The text was updated successfully, but these errors were encountered: