On Aug 19, 12:55 am, Pops <[EMAIL PROTECTED]> wrote: > What was you sending?
i wasn't sending anything - i just wanted to load the contents of an HTML snippet file (not a complete/well-formed HTML document) into a DIV. > We write our own web server and as such we conform to HTTP RFC > standards, and it was never a consideration to be aware of > "configuration" options for standard GET/POST required operations. I > mean, a web server either supports proper RFC 1945 (HTTP 1.0) or RFC > 2616 (HTTP 1.1) or it doesn't in which case, its broken :-) Apache can be configured to allow/disallow POST for certain extensions. On my provider they have POST to HTML disabled (presumably it is enabled for SHTML, and is definitely enabled for PHP). > bandwidh DSL speeds that differ in direction. Fast input (downloads), > slow output (uploads) created a "timing issue" which causes a TCP/IP > frame reset. The visual error for users was "PAGE NOT FOUND." No, the error was "method [POST] not allowed", and was/is a simple Apache config option. Since it is unusual to have .html files serve as dynamic file sources, disabling POST for them seems to be reasonable (but annoying for my case because on my local server it had worked, causing confusion after i tested it remotely). My assumption was that load() would respect the default settings set for ajax(), which i subsequently set to use GET, but load() appears to ignore those options. Using get() worked around the problem, in any case.
