+ update 2020: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means we will NOT develop new features and/or fix most of bugs. We left the tracker running in case somebody from community would like to work on it. Sorry for the inconvenience.
State: new 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.
It would be nice to have https support in the "Open via proxy" feature.
Yeah, that would be awesome, but it is not easy to do.
There have to be self generated SSL certificates to the same domain as target site,
and webbrowser usually does not permit this. It shows a warning on some browsers, other
browsers do not allow it at all (Firefox is pedantic for example).
That's why SSL exists - to not be intercepted or modified.