Home – New Forums Tech talk Weird Site Problem with FF Reply To: Weird Site Problem with FF

  • Total posts: 335

Hi Chris

You know, I’m still not convinced. :)

A 501 error is generated by the server, so it’s the request type (GET, POST etc) being generated by FF that was in error, not what FF is receiving in reply (if I read everything correctly)

Check out this again:

HTTP Error 501 Not implemented


The Web server (running the Web site) does not understand or does not support the HTTP method it finds in the HTTP data stream sent to it by the client (e.g. a Web browser or our CheckUpDown robot). The methods defined by the HTTP protocol are as follows:

OPTIONS: Find out the communication options available for a particular URL resource. Allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without a specific action involving transfer of data.
GET: Retrieve the information identified by the URL resource e.g. GET a particular Web page or image. The most common method by far.
HEAD: Identical to GET except that the server returns header information only, not the actual information identified by the URL resource. Useful to obtain metainformation about the entity implied by the request without transferring the entity-body itself. Often used to test hypertext links for validity, accessibility, and recent modification.
POST: Submit data to the Web server such as 1) post a message to a bulletin board, newsgroup or mailing list, 2) provide input data – typically from a CGI form – to a data-handling process, 3) add a record directly to a database.
PUT: Set (place/replace) the data for a particular URL to the new data submitted by the client. For example, upload a new Web page to a server.
DELETE: Remove the data associated with the URL resource. For example, delete a Web page.
TRACE: Run a remote, application-layer loop-back of the request message. Effectively a ‘ping’ which tests what data the Web server is receiving from the client.
CONNECT: Reserved for use with tunnelling (e.g. SSL) via a proxy server. This method is defined only for HTTP version 1.1, not the earlier version 1.0.

If the method in the request HTTP data stream is not one of the above, then a 501 error will result. Or the method may be valid but not actually supported by the Web server. This typically only happens for newer methods such as CONNECT when received by older Web servers.

Anyway, its still strange that *something* could cause FF to mangle what it sends to the web server. Perhaps its the way FF collected what it needed to POST back and got it all screwed up.

I would have loved to see exactly what FF was sending to the webserver!

Anyway, problem solved so it seems!