-
-
Notifications
You must be signed in to change notification settings - Fork 166
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
Virtualmin save_bkey.cgi script is called with wrong encoding type #959
Comments
Hi, Jamie, thanks for reporting! It happens because of unconventional form's action link, which links to something about I have made a patch to capture this kind of links for all calls. I have noticed that it takes literately forever to create a key and fails in most cases for me with an error:
It happens in Gray Theme as well. Not sure why it's happening. I think it should be checked. I ran it on my VM (CentOS 7). Surely we need to return the progressive output to the user on this page, telling what's going on. Jamie, make sure to let me know, in case you decide to make this part of the module progressive. For the future, I need always to know, when you add progressive output for certain pages. It has to be reflected on the theme as well to work correctly. |
Yeah, key generation can be slow (perhaps infinitely) on VMs due to lack of entropy. This is unfortunately un-avoidable :-( |
Sure, no problem. |
This was detected in https://www.virtualmin.com/node/54740
Basically, it looks like when the form on edit_bkey.cgi uses the form-data encoding type, save_bkey.cgi is called with no input. The actual URL that's requested is :
The text was updated successfully, but these errors were encountered: