: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means waiting times in the issue tracker are very long and mostly depend on community. Sorry for the inconvenience.
State: closed new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
Would be nice to have ability to completely replace any swf in cache via Proxy tool.
Do you mean FFDec has own folder somewhere in AppData to store that files?
Otherwise (depending on browser) it may be pain in the neck to find correct file and
Would be great to have special button for this purpose or some kind of remap feature - to
be able to set path to the replacing swf (remote or local).
Can't test it - looks like Proxy broken for me now. Can't see any new swf files in it (was
able to see old from prevous session, but no new files appear there).
For example: https://www.adobe.com/swf/software/flash/about/flashAbout_info_small.swf
I open it in latest Firefox. Proxy started, Sniff SWF checked, but nothing get captured.
I use nightly 328 version.
Just tried it with IE - same issue - nothing shows in Proxy as I load page with swfs.
If I press Clear now - I see columns headers change their names to A, B and C.
Looks like some errors happening under the hood.
Please try nightly 329 or later. The problem with Clear button, etc. should be fixed.
For the example you posted: It is HTTPS address. SSL encrypted content cannot be catched
in current version of FFDec.
There already exists an issue for it, but it is not easy task. Certificates for each
server must be generated automatically and some certificate import to browser is needed...
Not so simple. You know... that's why HTTPS is secure.