Viewing 8 replies - 1 through 8 (of 8 total)
  • Hello donburikun, we have a bug filed for this. Our internal reference number is FB1730. For debugging purposes, could you let us know what version of PHP you are running? You can see this on the Wordfence “Diagnostics” page. Thanks in advance!

    Thread Starter donburikun

    (@donburikun)

    Thank you for your reply. I am running WordPress 4.5.3 with PHP 5.5.

    Thread Starter donburikun

    (@donburikun)

    Please let me know if you require any further information.

    Hello donburikun,
    we have a bug filed but I can’t tell you when it will be fixed. We don’t have a lot of reports of this error. It happens with some particular URL structures. The URL you are seeing there (/register/?redirect_to=https://www.#########.com/create-listing/) do you recognize which plugin it belongs to? It’s not a basic WordPress URL.

    Thread Starter donburikun

    (@donburikun)

    Thank you for your reply. That is disappointing to hear. While you may not have many “reports” it can be seen by a simple google search that there are many sites with this issue (6050 at this time).

    Yes, this URL is from the theme I am using on my site (Classipress). Appreciate your response. Thanks again.

    Hello again,
    A verbatim Google search returns 60 results and virtually all of them are caused my malformed URLs. I see a few that look like they’re hacked too. Where are you getting the figure 6050?

    Hello,

    I’ve got the same problem (I use PHP 5.2):

    Warning: Cannot modify header information – headers already sent by (output started at /home/XXXXXXXXXXXX.com/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/request.php:329) in /home/XXXXXXXXXXXX.com/public_html/wp-includes/pluggable.php on line 1167

    Any ideas anybody?

    metalmate, you should definitely get your PHP upgraded to at least 5.6 (preferably 7). If you are unsure of how to do this, please reach out to your web host. We do not recommend using Wordfence with PHP 5.2.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Warning: parse_url’ is closed to new replies.