Embedded (Nested) x-www-url-formencoded string parsing in Laravel 9 | Laravel | Page 1

brave chasm Oct 27, 2022, 3:34 AM

#

I have a x-www-urlencoded string which contains a x-www-urlencoded string (I can't change the structure due to backwards compatibility)

Sample String:
Action=saveAccount&Pass=pass&Email=email&saveString=whichProfile%3D1%26item1%5Fnum%3D6&ver=750
(The client before sending saveString's result urlencodes the string, so, %3D = =, and %26 = &)

When this gets sent to laravel, it properly decodes it but saveString has a result of string so I can't access the properties inside easily, to remedy this, I attempted to make a new Request and pass the saveString's string as the body but unfortunately, it does not parse it, I checked all the middleware names, none of them had names that seemed like they would parse the input/body so I was wondering how to properly do this

# $save = $request->input('saveString')
$saveRequest = FormRequest::create('', 'POST', [], [], [], [], $save);

print_r($saveRequest->all());

($saveRequest->all() is empty and the input methods and such don't have the keys recognized which is my basis for assuming it isn't being parsed in the Request object (FormRequest))
(I put this in here so it won't get lost like it did in #help)

brave chasm Oct 27, 2022, 5:32 PM

#

If there is anything I can add to assist in figuring out this problem, please let me know! 🙂

brave chasm Oct 27, 2022, 5:57 PM

#

Ah, it's easy to overlook but I found it, they use parse_str in vendor/laravel/framework/src/Illuminate/Http/Client/Request.php in the parameters function but that still begs the question as to why it didn't do that by default when making an instance of FormRequest using ::create

#Embedded (Nested) x-www-url-formencoded string parsing in Laravel 9