Hi, I recently faced an issue related to the override-ext-ajax: when issuing a GET ajax request to query geoserver for a wfs getcapabilities, the content-type "application/x-www-form-urlencoded" is automatically added by the ext ajax override, and this causes geoserver to return an exception (working ok with no content type). I don't know if the problem is related to geoserver, but reading the w3c form element [1], it is written that the content type (which default value is "application/x-www-form-urlencoded") is used to submit the form to the server *when the value of method is "POST"*.
The problem I encounter has been introduced by ticket #170 [2]. Bart, you may have an opinion on this? If it makes sense to you, I can create a ticket and provide a patch so that content type "application/x-www-form-urlencoded" is used only when method is POST. Cheers, Bruno [1] http://www.w3.org/TR/html401/interact/forms.html#h-17.3 [2] http://trac.geoext.org/ticket/170 -- Bruno Binet Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac, Cedex Mail : [email protected] http://www.camptocamp.com _______________________________________________ Dev mailing list [email protected] http://www.geoext.org/cgi-bin/mailman/listinfo/dev
