Thread Starter
doliii
(@doliii)
Hi there,
Thank you for the prompt response and insight!
That makes perfect sense. If the escaping function intended for the debug output was inadvertently applied to the variable used for the actual HTTP request, it perfectly explains the sudden appearance of the double URL encoding (%25…) that tripped our WAF’s evasion rules.
Your plan to switch the Bulk API requests to POSTs is exactly the perfect solution! Moving the payload to the POST body will not only resolve this double-encoding WAF conflict but also make the plugin much more robust against strict enterprise firewall rules (like URI length limits) in the future.
We will happily stay on version 1.1.6 and look forward to the next release with the POST implementation.
Thank you again for your excellent support and for maintaining such a great plugin!
Best regards,