Recently we've been setting up a system where work is allocated outside of app engine and sends back to an App Engine application a JSONified Map containing a byte array that represents a pdf file's contents, which is then uploaded to Google Drive. Within a local configuration the the flow of the pdf is uploaded and appears correctly in Drive. However, when deploying this to an actual App Engine Node the file does not appear "valid".
After debugging and diagnosis the issue is with the contents of special characters within the strings being passed, despite being UTF-8 encoded at every possible point. Originally URL Encoding was being used and failing still, however, after searching a solution proposed to Base64 encode the array of bytes, and thus this resolved the problem and Document uploaded correctly. The question therefore is what is the difference with respect to byte array handling that would require explicit base 64 encoding to handle special characters between a localised App Engine environment and a deployed instance? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/uuE7XSA7ABQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
