HTTP Error Code 406 Not Acceptable

I have WebAssits version 2.3.5. And now always show me this message to conect with the database. I used dynamic Mysqli Connection. Thanks

It is probably an issue with the Dreamweaver Site Definition. If you export your site definition and send it as a private attachment I will be able to reproduce the problem and debug it for you.

see attach. I how i can do it, every time i want to buid a web site. Thanks

Please upload your connection file so I can test it. So far I see that your testing server Web URL starts with http:// but your site is set to force https://

l can't confirm that is the only issue without the connection file to test as well.

Originally Said By: Ray Borduin

  Please upload your connection file so I can test it. So far I see that your testing server Web URL starts with http:// but your site is set to force https://

l can't confirm that is the only issue without the connection file to test as well.  

See atachments

The HyperText Transfer Protocol (HTTP) 406 Not Acceptable client error response code indicates that the server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers, and that the server is unwilling to supply a default representation.

In layman's terms: I think your server has an access rule defined that is preventing Dreamweaver from browsing the site directly. It might be a ModSecurity setting that only allows browsers to access web pages (not Dreamweaver) as a security measure.

Who hosts the site? They may be able to access the ModSecurity log file to see the issue and enable dreamweaver to access the necessary database files. Dreamweaver tries to post to a hidden file in the _mmServerScripts directory. This error means that your server is rejecting the post and refusing to return the necessary data.

I tried to disable mod_security by adding a .htaccess file to the _mmServerScripts folder, but that didn't seem to work. I think your hosting company may be able to shed some light on it by looking at the server logs when accessing that folder.