Jump to content
Ketarin forum

Help on POST data & odd redirect for UltraUXThemePatcher


bendingkedge
 Share

Recommended Posts

I've been trying to figure this one out but nothing seems to work. I've tried all kinds of combinations with the POST data. Adding things, taking things away. I've added the cookies to the POST in different forms and removed them completely. I admit, I don't entirely know what I'm doing, just what I've seen in this forum on POST data and redirects.

Here's the page for the download: https://mhoefs.eu/software_uxtheme.php?lang=en

I'm posting the latest iteration of this XML. Any help is greatly appreciated.

UltraUXThemePatcher (x86) (Setup).xml

Link to comment
Share on other sites

This is another one of those situations where you *could* go to all the effort of recreating the form, or you could just convert it to a GET request instead of a POST request and it works fine. I've tried that link in several browsers without session ties and it works fine in all of them. You might need to change the user-agent for the app profile, but it should work fine once it's using that GET-form URL. The site might change various field values at some point, and you could easily map them out using variable assignments instead. I doubt it will happen often enough to make it worthwhile to parse the page, though. There are only two fields and the structure looks to be very simplistic. 

 

Link to comment
Share on other sites

Thanks, shawn! I think I vaguely recall seeing you mention that to someone else in another post, probably an old one. Yeah, I've no inclination to recreate POST crap when a GET will work just fine. Can you tell me how you figured out the conversion so I can use that in the future? And yeah, just tried it using only that url and a mozilla ua and it works great! :D

Edit: Never mind. I think I figured it out. Just take the Form data viewed as source and add that to the end of the download url after adding a "?". Right?

Link to comment
Share on other sites

Yes, you just use equal signs separating each field/value pair, and ampersands separating each form element.

url ? field1 = value1 & field2 = value2 & field3 = value3

Be aware that form elements (fields and values) using certain characters MUST be URL-encoded in order to appear in a GET request (or in the DATA element of a POST request). This includes all percentage signs, white space, quotes, equals, ampersands, and several other characters. URL-encoding is NOT the same thing as HTML-encoding. URL-encoding uses a percentage sign then the two hexadecimal values of the ASCII table for the character. HTML encoding uses an ampersand then either a named value or a numeric value followed by a semicolon. None of this applied to the specific form in this instance.

The RFCs that explain all of this are a great read if you want to understand the how and why of all this crap. If you get bored you should just read them all. Really

 

Link to comment
Share on other sites

Thanks, shawn! I appreciate the explanation. Yeah, I'm aware about the percentage and URL-encoding vs HTML encoding, such as %20 for a space, but appreciate your mention of it. It's a fair reminder. And thanks for the references. They appear to be a detailed breakdown of URI elements. Some interesting info.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.