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

Some AMF messages do not parse, just show blank output #1

Open
gingeleski opened this issue Jun 5, 2018 · 4 comments
Open

Some AMF messages do not parse, just show blank output #1

gingeleski opened this issue Jun 5, 2018 · 4 comments
Labels
bug Something isn't working

Comments

@gingeleski
Copy link
Member

Noticing for my use case not all AMF messages are decoding.

Shorter ones seem to do OK, longer ones do not. From content type and the raw response content I can see these are AMF messages.

What's contributing beyond the length I am not yet sure. Will update as appropriate.

@gingeleski gingeleski added the bug Something isn't working label Jun 5, 2018
@gingeleski
Copy link
Member Author

Think bringing in the code from the yyjdelete fork may help.

Could very well be UTF8 thing and at least one of those commits improves upon that.

@gingeleski
Copy link
Member Author

Trying this file which has the commit of yyjdelete's Plugin.cs

@gingeleski
Copy link
Member Author

Did not resolve my issues. Keeping the changes as I think they're improvements.

@gingeleski
Copy link
Member Author

Ended up trying out Charles Proxy, which can open my saved Fiddler session archives and has awesome AMF parsing out-of-the-box. Would highly recommend. So for my purposes I probably won't pursue this plugin further.

If someone else wants to tackle this, go wild.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant