The problem seems to be PHP related, can someone confirm?

Can you attach the Xdebug debugging log, and the files that you used to this report? You can learn at https://xdebug.org/reporting-bugs#step-debugger on how to create a debugging log.

Can you provide the requested feedback please?

@derick

Hi, I'm sorry I no longer have the files as I had to adapt the code, no logs either but I have pasted the very same minimal code to reproduce the bug, if this can help I was using Xdebug with the equivalent plug-in for Sublime Text, back then I remember I confirmed multiple times it is showing the string as described while not actually being Base64 however at some point it was read as a real Base64 the problem was most probably caused by text containing ÉGOÏSTE I had to rewrite the client part to normalize strings and only accept "normal" letters and convert this to EGOISTE this solved the bug on Xdebug and/or PHP whoever is at this. I noticed the snippet above stripped the opening tag, not sure why it didn't let me paste the snippet correctly. Was you able to run the above code in the same setup and replicated the issue?

I wouldn't have asked for the logs if I could reproduce it with your example — but that is mostly because it's not a complete case. It's not something I can download and run, with it working immediately.

@derick

Ok, I'll create a project with minimum code to replicate the issue. Will update once ready.

Hi @nym,

Did you find the time to do this?

cheers,
Derick

@derick,

I was drained in a work I had to deliver, I'll do this test project on saturday at the latest and upload it here.

@derick,

Wow I wrote a lenghty text and token expired, I'll be more concise, download the zip and read the comments inside to fill-in-the-blanks before you test, load the client manifest as a temporary add-on for firefox, as soon and you add it, the plug-in will open a new window to a website with ?r parameter the website must be your XAMPP configured endpoint.

See the comments inside the .js (client) and php (server) files and if it is not clear let me know.

I don't use Sublime, and I don't quite understand why you're asking me to install a temporary Firefox plugin?

There should be no need for this surely, as Xdebug is a debugger for PHP - it doesn't interact with anything JavaScript related either.

@derick,

It was to reproduce my environment entirely. The temporary plug-in is how I send the URL call to the PHP, the JavaScript portion is on the plug-in to trigger the PHP. Once there and using Xdebug plug-in for Sublime, you can replicate the issue. The plug-in for Sublime is a "glue" to have Xdebug "talk" to Sublime and debug using it.

I have no idea what you just said.

Xdebug does not interact with JavaScript. JavaScript might start a request, but then Xdebug is only concerned with the request once it hits the web server and PHP.

Show me the interaction between your HTTP client and your Webserver/PHP? Tools like Wireshark can do that.

@derick,

That's correct, it was to reproduce my environment. On May 6th you asked for a sample project with minimum code to reproduce the bug, I provided you this and instructions to replicate. The JavaScript is how I create the string passed to the PHP, you don't need to run the plug-in very time but only once to generate the string for you, then you can set this string to start your PHP project and see that once the Xdebug hits sublime debug, the error will raise.

So please provide the bare minimum. I do not need any plugins for normal debugging, so why do I need that now. I also don't have Sublime. If there is a bug in Xdebug, then you must be able to reproduce it with simple HTTP requests.

@derick,

The plug-in might be a factor in how it encodes the string, I'd suggest you have the plug-in (which is itself a bare minimum) generate the relevant string and then use it to call the php script as an ? argument for you debug purposes. Sublime should not the cause, but Xdebug for Sublime might be part of the process. If you want to reproduce my environment then use the provided setup, deducting from it will be something we can do once you have replicated the bug with the same situation, then we can narrow it deducting Sublime / plug-in etc..

How the plugin encodes the string is not of my concern. It might as well be a bug there.

I asked before (https://bugs.xdebug.org/view.php?id=2257#c7021) to provide the network traffic to show your case. You can use Wireshark to do that. Feel free to attach the generated pcapng file.

If you're not willing to demonstrate that it is Xdebug that is the problem, then I won't be able to assist further.

@derick,

Sound like you prefer to hide the bug under the carpet and pretend everything is fine. When you do testing the first step is to replicate the environment, then the user behavior. After this, you can subtract elements and narrrow it down, not before, this is general testing not rocket science. I provided you with the minimal code to replicate my environment and beharior. It is up to you if you prefer to lift the carpet and hide this or do some real testing. Either way I'm done here. Best.