I've added modifications to collect to encrypt submissions when they
are saved, and decrypting it when opened again. However when uploading
to Aggregate, collect shows error 500 Internal Server Error.
From what i understand, collect finds the submission xml, adds it to
"entity", finds other files within the folder and adds it, then sends
it all together to Aggregate.
What i did was decrypt the file and overwrite so that it contains
plain text again, let collect find and add the file, then encrypt it
again once the sending is complete but before it checks the server's
reply. Is there something else that Collect does that i'm not aware?
If the Aggregate server is running on Appspot, look at the Logs for the
server (reachable from the appspot administration page for the server via https://appengine.google.com/ ). A 500 error should log an error. If you
don't see anything, display logs at the Info level.
What version of Aggregate are you using?
If you copy the submission off the phone and upload it via the submission
upload page of Aggregate, does that also give you a 500 error? ( This is
now on the Management / Submission Admin sub-tab in 1.0 ).
Note that Collect will attempt to upload all the files in the directory, so
if you still have the encrypted file, it would attempt to upload that as
well. I don't think that would cause a problem, though, just extra wasted
bandwidth.
Mitch
···
On Fri, Oct 21, 2011 at 7:28 PM, Kee wrote:
I've added modifications to collect to encrypt submissions when they
are saved, and decrypting it when opened again. However when uploading
to Aggregate, collect shows error 500 Internal Server Error.
From what i understand, collect finds the submission xml, adds it to
"entity", finds other files within the folder and adds it, then sends
it all together to Aggregate.
What i did was decrypt the file and overwrite so that it contains
plain text again, let collect find and add the file, then encrypt it
again once the sending is complete but before it checks the server's
reply. Is there something else that Collect does that i'm not aware?
I tried ur suggestion. manual submission gives internal error if
uploaded the encrypted file, so i'll try decrypting earlier
···
On Oct 25, 1:43 am, Mitch Sundt wrote:
> If the Aggregate server is running on Appspot, look at the Logs for the
> server (reachable from the appspot administration page for the server viahttps://appengine.google.com/). A 500 error should log an error. If you
> don't see anything, display logs at the Info level.
>
> What version of Aggregate are you using?
>
> If you copy the submission off the phone and upload it via the submission
> upload page of Aggregate, does that also give you a 500 error? ( This is
> now on the Management / Submission Admin sub-tab in 1.0 ).
>
> Note that Collect will attempt to upload all the files in the directory, so
> if you still have the encrypted file, it would attempt to upload that as
> well. I don't think that would cause a problem, though, just extra wasted
> bandwidth.
>
> Mitch
>
> On Fri, Oct 21, 2011 at 7:28 PM, Kee wrote:
> > I've added modifications to collect to encrypt submissions when they
> > are saved, and decrypting it when opened again. However when uploading
> > to Aggregate, collect shows error 500 Internal Server Error.
>
> > From what i understand, collect finds the submission xml, adds it to
> > "entity", finds other files within the folder and adds it, then sends
> > it all together to Aggregate.
>
> > What i did was decrypt the file and overwrite so that it contains
> > plain text again, let collect find and add the file, then encrypt it
> > again once the sending is complete but before it checks the server's
> > reply. Is there something else that Collect does that i'm not aware?
>
> --
> Mitch Sundt
> Software Engineerhttp://www.OpenDataKit.org
> University of Washington
> mitchellsu...@gmail.com
also, are the encryption patches something you can share with the
wider community?
···
On Tue, Oct 25, 2011 at 00:46, Kee wrote:
> Thanks for replying,
>
> i'm using Aggregate 1.0 RC3 on TomCat
>
> I tried ur suggestion. manual submission gives internal error if
> uploaded the encrypted file, so i'll try decrypting earlier
>
> On Oct 25, 1:43 am, Mitch Sundt wrote:
>> If the Aggregate server is running on Appspot, look at the Logs for the
>> server (reachable from the appspot administration page for the server viahttps://appengine.google.com/). A 500 error should log an error. If you
>> don't see anything, display logs at the Info level.
>>
>> What version of Aggregate are you using?
>>
>> If you copy the submission off the phone and upload it via the submission
>> upload page of Aggregate, does that also give you a 500 error? ( This is
>> now on the Management / Submission Admin sub-tab in 1.0 ).
>>
>> Note that Collect will attempt to upload all the files in the directory, so
>> if you still have the encrypted file, it would attempt to upload that as
>> well. I don't think that would cause a problem, though, just extra wasted
>> bandwidth.
>>
>> Mitch
>>
>> On Fri, Oct 21, 2011 at 7:28 PM, Kee wrote:
>> > I've added modifications to collect to encrypt submissions when they
>> > are saved, and decrypting it when opened again. However when uploading
>> > to Aggregate, collect shows error 500 Internal Server Error.
>>
>> > From what i understand, collect finds the submission xml, adds it to
>> > "entity", finds other files within the folder and adds it, then sends
>> > it all together to Aggregate.
>>
>> > What i did was decrypt the file and overwrite so that it contains
>> > plain text again, let collect find and add the file, then encrypt it
>> > again once the sending is complete but before it checks the server's
>> > reply. Is there something else that Collect does that i'm not aware?
>>
>> --
>> Mitch Sundt
>> Software Engineerhttp://www.OpenDataKit.org
>> University of Washington
>> mitchellsu...@gmail.com
If the Aggregate server is running on Appspot, look at the Logs for the
server (reachable from the appspot administration page for the server
viahttps://appengine.google.com/). A 500 error should log an error. If
you
don't see anything, display logs at the Info level.
What version of Aggregate are you using?
If you copy the submission off the phone and upload it via the
submission
upload page of Aggregate, does that also give you a 500 error? ( This
is
now on the Management / Submission Admin sub-tab in 1.0 ).
Note that Collect will attempt to upload all the files in the directory,
so
if you still have the encrypted file, it would attempt to upload that as
well. I don't think that would cause a problem, though, just extra
wasted
bandwidth.
I've added modifications to collect to encrypt submissions when they
are saved, and decrypting it when opened again. However when uploading
to Aggregate, collect shows error 500 Internal Server Error.
From what i understand, collect finds the submission xml, adds it to
"entity", finds other files within the folder and adds it, then sends
it all together to Aggregate.
What i did was decrypt the file and overwrite so that it contains
plain text again, let collect find and add the file, then encrypt it
again once the sending is complete but before it checks the server's
reply. Is there something else that Collect does that i'm not aware?
--
Mitch Sundt
Software Engineerhttp://www.OpenDataKit.org
University of Washington mitchellsu...@gmail.com
i'm using Aggregate 1.0 RC3, but i got the uploading part working now.
I put the decryption process before "InstanceUploaderTask" gets the
instance file, specifically before this line:
File instanceFile = new File(instance);
May i know how to create a patch through Eclipse? I see the option
there, but not really sure how it works. Was gonna request a code
review, but i suppose this could be better
first, pull all the code and make sure you are up to date with trunk.
if there are conflict, resolve them.
then in eclipse, right click on your project, go down to team menu and
and export a patch. attach that patch to a new issue and we can take a
look there. if you have a publicly accessible repo, include that link
in the issue.
···
On Thu, Nov 3, 2011 at 07:45, Kee wrote:
> Sry for this late reply
>
> i'm using Aggregate 1.0 RC3, but i got the uploading part working now.
> I put the decryption process before "InstanceUploaderTask" gets the
> instance file, specifically before this line:
>
> File instanceFile = new File(instance);
>
> May i know how to create a patch through Eclipse? I see the option
> there, but not really sure how it works. Was gonna request a code
> review, but i suppose this could be better