Skip to content
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

can not record some post requests when click on certain buttons #20

Open
siyaoli opened this issue Sep 9, 2016 · 4 comments
Open

can not record some post requests when click on certain buttons #20

siyaoli opened this issue Sep 9, 2016 · 4 comments

Comments

@siyaoli
Copy link

siyaoli commented Sep 9, 2016

Hi Joe,

I am a big fan of Gargl. Now I have a problem, when I click on some certain buttons, I can get post requests of XHR from network tab, but I cannot get these records from Gargl. The website uses a lot of ajax. Could you please release a new version or give me some idea about how to make a complete record on all these XHR?

Thank you so much!

@jodoglevy
Copy link
Owner

Hi,
What page are you doing this from, and what URLs are not showing up in Gargl?

@arpsmack
Copy link

I had this issue messing around with Trivia Crack just recently. The POST request it issues to assign a card to a slot seems to get completely ignored by the chrome devtools.

The URL is https://api.preguntados.com/api/users/@user-id@/gacha-slots/@slot-id@/cards

This could be because the POST request has a payload of "{id: @card-id@}". I don't think any of the other POST requests have a payload and they all seem to get tracked by gargl just fine.

@arpsmack
Copy link

Err, sorry, let me clarify. The POST request shows up in the network view in the chrome devtools, but for some reason the request is not being passed to gargl's chrome.devtools.network.onRequestFinished listener.

"completely ignored by the chrome devtools" probably wasn't the correct choice of words.

@jodoglevy
Copy link
Owner

Weird. Just looked into this a bit. It does seem like Chrome is not firing the handler passed to chrome.devtools.network.onRequestFinished as you said, specifically for cross origin POST requests. Regular POST requests, and cross origin GET requests, seem to show up fine. But for cross origin POST requests, only the OPTIONS request before the POST shows up.

I don't think its related to the POST request body, because the POST requests to https://apps.facebook.com/ajax/bz on the same page show up fine in Gargl, and they have a body. But they are not cross-origin, which is why I think the issue is related to that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants