500 Internal Server Error after setting “Use Apache (mod_headers) to send header

  • Resolved patadata

    (@patadata)


    7 years, 10 months ago

    Hi,

    As described in the subject I went into “Advanced settings” and changed from “Use PHP to send headers (deprecated)” to “Use Apache (mod_headers) to send headers”. I did that since it said “deprecated”, so I thought it would be 2 best practise to change it, but then it stopped working.

    I have been trying to find out where I can find the setting for this and change it back without any luck 🙁

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Dimitar Ivanov

    (@zinoui)

    7 years, 10 months ago

    @patadata

    500 Internal Server Error often is a result of misconfiguration or syntax error in the .htaccess file. The reason also can be a missing (not loaded) Apache module.

    Can I see your .htaccess?

    • This reply was modified 7 years, 10 months ago by Dimitar Ivanov. Reason: A typo
    Plugin Author Dimitar Ivanov

    (@zinoui)

    7 years, 8 months ago

    Prior the v1.10.4 of this plugin, there was a bug when all of the following are met:
    – PHP is running as CGI, FastCGI, PHP-FPM
    – the “Apache” mode of this plugin is active
    – Cookie security is ON and HttpOnly and/or Security is checked

    In that particular case the server throws a 500 Internal Server Error.

    However, the bug was fixed. If this is your case just update the plugin.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘500 Internal Server Error after setting “Use Apache (mod_headers) to send header’ is closed to new replies.