Is http://code.google.com/p/googleappengine/issues/detail?id=4265 related?
I'm getting base64 back after the upload, which I pretty sure the server
should decode it. I'm not sure about character issues. Also, blobinfo is
recording the wrong file byte size for base64 files, which after comparing
On 26 October 2010 10:28, Kenneth goo...@kmacleod.ie wrote:
This is a pretty shocking bug (or lack of documentation?) from
Google. There doesn't appear to be a consistent way to decode the
post results that come from the BlobstoreUploadHandler. There was a
bug in the issues list for this but
Chris,
I really appreciate the information, but I would like to hear from
Google about this bug.
Q1. Are you going to fix this bug in near future?
Q2. Do you have any suggested way to work-around this bug, which won't
cause compatibility issue in future when you fix this bug?
Satoshi
On Nov 13,
I wrote a test code, and verified this bug (it happens in Japanese as
well).
Here is the form:
form id='form_upload' action=$(_upload_url) method=POST
enctype=multipart/form-data
div class='dialog_field'
div class='field_name'File:/div
input type='file' name='file' /
I also wrote an upload code in Objective-C, explicitly specifying the
Content-Type: text/plain; charset=UTF-8,
but got the same result as HTML form sample above.
日本語 becomes 5pel5pys6Kqe
Satoshi
On Nov 13, 7:01 am, Satoshi satoshi.nakaj...@gmail.com wrote:
I wrote a test code, and verified
In Python the text is encoded as quoted printable (I think).
See issue
#3761http://code.google.com/p/googleappengine/issues/detail?id=3761and
Stack
Overflow
questionhttp://stackoverflow.com/questions/3624226/encoding-problem-in-app-engine-when-submitting-multipart-form-data-forms.
I've worked
I ran into the same issue.
Has anyone found the corresponding issue in the bug tracker (or a nice
workaround)?
Michael.
On 26 Okt., 09:28, Kenneth goo...@kmacleod.ie wrote:
This is a pretty shocking bug (or lack of documentation?) from
Google. There doesn't appear to be a consistent way to
Do you guys have any sample code? I'm testing this and seeing that the local
dev server gives me some strange characters (I'm using Java). What does the
form look like? How are you reading the input from the form submission?
--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger:
This is a pretty shocking bug (or lack of documentation?) from
Google. There doesn't appear to be a consistent way to decode the
post results that come from the BlobstoreUploadHandler. There was a
bug in the issues list for this but I can't find it. I should put in
another one really but there
Does that happen everytime on the blobstore only api? or regular text -
datastore?
One more thing, there is a huge difference on how the text is being
displayed on the datastore dashboard. are you sure its being saved as
base64? the page encoding for the production datastore browser is
massed up
This happens when text fields are sent via POST and go through the
Blobstore upload handler.
When English text is used I get the text.
When Hebrew is used I get a base64 string...
I'm not looking at the datastore dashboard. I'm looking at the actual
POST data (via logging)
On Aug 3, 10:18 am,
it outputs as a base64 string? im guessing the post is multi-part post
right?
On Aug 3, 10:39 am, ekampf eka...@gmail.com wrote:
This happens when text fields are sent via POST and go through the
Blobstore upload handler.
When English text is used I get the text.
When Hebrew is used I get a
yep..
It doesnt happend on the local dev server... its definately something
undocumented happening on AppEngine
On Aug 3, 10:54 am, alon alon.car...@gmail.com wrote:
it outputs as a base64 string? im guessing the post is multi-part post
right?
On Aug 3, 10:39 am, ekampf eka...@gmail.com
13 matches
Mail list logo
