I think the bug is in applications/admin/static/ajax_editor.js
function prepareMultiPartPOST(data)
Can you replace the function with
function prepareMultiPartPOST(data) {
var boundary = 'sPlItME' + Math.floor(Math.random()*10000);
var reqdata = '--' + boundary;
//console.log
(data.length);
for (var i=0;i < data.length;i++)
{
reqdata += '\r\ncontent-disposition: form-data; name="' +
data[i].N\
ame + '"\r\n\r\n';
reqdata += data[i].Data;
reqdata += '\r\n--' + boundary;
}
return new Array(reqdata,boundary);
}
and run give it a try?
I did not write it and I am not sure how to fix but I can try...
Massimo
On Mar 5, 10:31 am, Guido Kollerie <gu...@kollerie.com> wrote:
> On 4-mrt-2009, at 14:49, mdipierro wrote:
>
> > I cannot reproduce this. Can you add some print statmenets to
> > applications/admin/controllers/default.py and try determine if is a
> > browser issue (as I think), a JS issue or a server side issue?
>
> I installed the Firefox plugin HttpFox to see what is being submitted to
> the server. This is what HttpFox showed me as the request headers being
> sent:
>
> (Request-Line) POST /admin/default/edit/images/models/db.py HTTP/
> 1.1
>
> Host: 127.0.0.1:8000
> User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X
> 10.5; en-US; rv:1.9.0.6) Gecko/2009011912 Firefox/3.0.6
> Accept: application/json, text/javascript, */*
> Accept-Language: en-us,en;q=0.5
> Accept-Encoding: gzip,deflate
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Keep-Alive: 300
> Connection: keep-alive
> Content-Type: multipart/form-data;
> charset=UTF-8;boundary="sPlItME8768"
> X-Requested-With: XMLHttpRequest
> Referer:
> http://127.0.0.1:8000/admin/default/edit/images/models/db.py
> Content-Length: 872
> Cookie: session_id_welcome=127-0-0-1-
> f825c08d-503f-4add-9528-22784d5456b1;
> session_id_admin=127-0-0-1-83f3fd40-abd9-4f53-beb1-60f4a78fd042
> Pragma: no-cache
> Cache-Control: no-cache
> --sPlItME8768: undefined
> content-disposition: form-data; name="data"
> db=SQLDB("sqlite: //storage.db")
>
> Notice the last request header? Markus' assessment seems correct in that
> it happens when the first line of the text area contains a colon. For
> some strange reason the line is then interpreted a request header. I
> haven't seen this before in any browser, let alone in both Safari and
> Firefox. Hence I am inclined to believe it has to do with the
> Javascript on the edit form.
>
> > Did this work with 1.55?
>
> Don't know; I only started playing with Web2py starting with version
> 1.57
>
> --
> Guido
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
