Bad Request

The server could not process your request due to a syntax error.

I just bought Filemaker Pro 5.5 unlimited. With mozilla and internet explorer everything works oke but OmniWeb gives that error. I don't know what to do because everything worked fine with Filemaker Pro 4.1

I searched in this forum and found about spaces but that is not the problem here. OmniWeb won't even load an url to an image.

Are you running 5.5v2? With either 5.5v3 or 5.5v4 of Web Companion.

All the best.

Garry

no, just installed the thing. I am trying to update it right now but the installer is very very slow (waiting for all applications to quit, but all applications are already turned off)

edit: waiting for an hour now, don't think that is good.

I updated the hard disk to a 60GB disk so I had to reinstall everything. the update worked with 10.1.4 but does not work with 10.1.5

oke, everything is updated to the latest version of filemaker/web companion but it still does not work

Omni replied with:

The problem appears to be caused by a bug in their web server's handling of the Accept-Language header (defined in RFC 2616 section 14): it returns an error whenever you send an Accept-Languages header containing the fallback language range "*" (which we use to tell the server to go ahead and send something even if nothing is available in one of the preferred languages which we've specifically requested).

This leaves us with no way to specify to their server that while we prefer the languages from the user's preferences, we're willing to accept content in any other language as well.

OmniWeb does have an override setting for the Accept-Language header, which you can set to change your Accept-Languages header to something else. Assuming you don't actually visit any web sites where your language settings matter, you could simply do this to work around the bug in their server:

defaults write com.omnigroup.OmniWeb OWHTTPSessionAcceptLanguageOverride ""

Setting the override to the empty string signals to OmniWeb that it shouldn't send the header at all.

(this topic should be moved to an other section I think, sorry for this)

I got this error too, when I ran a script from unlimited which opened multiple databases served by fm server 5.5

When I manually opened the db's, no problem. Annoying, though...