Question

I have installed TWiki on a new server. /bin/configure displays fine. I made the required changes to the paths, and clicked Next.

This gave me the following error:

406 Not Acceptable

An appropriate representation of the requested resource /bin/configure could not be found on this server.

I have since edited the /lib/LocalSite.cfg file manually, and TWiki works in general. However, I can't get configure to get past the first screen

Environment

-- EdMcDonagh - 16 May 2006

Answer

If you answer a question - or have a question you asked answered by someone - please remember to edit the page and set the status to answered. The status is in a drop-down list below the edit box.

A shot into the blue: Have you mod_security enabled? The "Next" button triggers a POST request which may violate one of the module's rules. The server's error log should have detailed information then.

-- HaraldJoerg - 17 May 2006

Maybe not so much into the blue!

mod_security: Access denied with code 406. Error parsing multipart parameters: Error normalising parameter value: Invalid Unicode encoding: invalid byte value [severity "EMERGENCY"]

Is there any part of mod_security that needs to be tweaked? My config is here. Or does it just not work with TWiki? If so, it is not so terrible as the server is not exposed to the outside world. However, it was installed with the rest of apache on fedora core 5, and I'm not sure how you would disable it!

Thanks for your help.

-- EdMcDonagh - 23 May 2006

In your mod_security.conf, I'd give a try to

    # Unicode encoding check
    SecFilterCheckUnicodeEncoding Off
    # was: SecFilterCheckUnicodeEncoding On

If you want to disable mod_security completely, simply switch the first variable, SecFilterEngine, to Off. But I wouldn't go that far.

-- HaraldJoerg - 24 May 2006

That worked fine. Thanks very much for your help.

For anyone else stuggling with this, the mod_security.conf file is located in /etc/httpd/conf.d/ on Fedora Core 5.

Also remember to restart the httpd service or any changes won't take effect!

-- EdMcDonagh - 25 May 2006

Hello,

This workaround doesn't work with ModSecurity 2, which comes with the latest Fedora Core 5 distribution.

The structure of the ModSecurity 2 files are different, and the statement that generates the error situation is located at:

/etc/httpd/modsecurity.d/modsecurity_crs_40_generic_attacks.conf

# Command injection SecRule ARGS|ARGS_NAMES|REQUEST_HEADERS ...

I've had to comment this line to be able to run Configure correctly.

-- JoaquimFreitas - 16 Apr 2007