Eternal 'Sending form' dialog problem

So I have some more insight on this. It seems to only happen during
sends when the authentication box pops up. So for example, the first
send since the app is started. I assume this box pops up because the
credentials have yet to be saved in the http session.

Anyway, I looked at the requests and responses when the box stays up
and when it goes away properly. Here's what I'm seeing. (Keep in mind
this is a custom aggregator so the problem could be in the way I'm
handling the requests.)

BAD

··· -----------

Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:51 -0400
Completed 401 Unauthorized in 1ms

Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:52 -0400
Completed 401 Unauthorized in 60ms

Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400
Completed 401 Unauthorized in 1ms

Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400
Completed 204 No Content in 170ms (Views: 36.0ms | ActiveRecord: 2.4ms)

Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400
Completed 401 Unauthorized in 16ms

Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:58 -0400
Completed 201 Created in 969ms (Views: 1.1ms | ActiveRecord: 39.6ms)

GOOD

Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400
Completed 401 Unauthorized in 1ms

Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400
Completed 204 No Content in 153ms (Views: 2.1ms | ActiveRecord: 3.4ms)

Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400
Completed 401 Unauthorized in 4ms

Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400
Completed 201 Created in 591ms (Views: 1.2ms | ActiveRecord: 58.8ms)

So it seems there are two extra requests, one HEAD and one POST that
are made at the beginning of the bad chain. I have no idea why. Any
ideas? Am I returning the right things here? It seems like a bit of a
bummer that the app is making two post requests even when it works,
but maybe this is how Basic authentication works? I'm not sure...

Anyone?

··· On 25 July 2011 12:17, Thomas Smyth wrote: > So I have some more insight on this. It seems to only happen during > sends when the authentication box pops up. So for example, the first > send since the app is started. I assume this box pops up because the > credentials have yet to be saved in the http session. > > Anyway, I looked at the requests and responses when the box stays up > and when it goes away properly. Here's what I'm seeing. (Keep in mind > this is a custom aggregator so the problem could be in the way I'm > handling the requests.) > > > BAD > ----------- > > Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:51 -0400 > Completed 401 Unauthorized in 1ms > > Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:52 -0400 > Completed 401 Unauthorized in 60ms > > Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 > Completed 401 Unauthorized in 1ms > > Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 > Completed 204 No Content in 170ms (Views: 36.0ms | ActiveRecord: 2.4ms) > > Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 > Completed 401 Unauthorized in 16ms > > Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:58 -0400 > Completed 201 Created in 969ms (Views: 1.1ms | ActiveRecord: 39.6ms) > > > GOOD > -------------- > > Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 > Completed 401 Unauthorized in 1ms > > Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 > Completed 204 No Content in 153ms (Views: 2.1ms | ActiveRecord: 3.4ms) > > Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 > Completed 401 Unauthorized in 4ms > > Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 > Completed 201 Created in 591ms (Views: 1.2ms | ActiveRecord: 58.8ms) > > > So it seems there are two extra requests, one HEAD and one POST that > are made at the beginning of the bad chain. I have no idea why. Any > ideas? Am I returning the right things here? It seems like a bit of a > bummer that the app is making two post requests even when it works, > but maybe this is how Basic authentication works? I'm not sure... >

carl's the most familiar with the networking code and he's in india on
a deployment. it's going to take some time before he can track this
down. in the meanwhile, does any of this happen if you try it against
an app engine instance with auth?

··· On Tue, Jul 26, 2011 at 12:51, Thomas Smyth wrote: > Anyone? > > On 25 July 2011 12:17, Thomas Smyth wrote: >> So I have some more insight on this. It seems to only happen during >> sends when the authentication box pops up. So for example, the first >> send since the app is started. I assume this box pops up because the >> credentials have yet to be saved in the http session. >> >> Anyway, I looked at the requests and responses when the box stays up >> and when it goes away properly. Here's what I'm seeing. (Keep in mind >> this is a custom aggregator so the problem could be in the way I'm >> handling the requests.) >> >> >> BAD >> ----------- >> >> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:51 -0400 >> Completed 401 Unauthorized in 1ms >> >> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:52 -0400 >> Completed 401 Unauthorized in 60ms >> >> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >> Completed 401 Unauthorized in 1ms >> >> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >> Completed 204 No Content in 170ms (Views: 36.0ms | ActiveRecord: 2.4ms) >> >> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >> Completed 401 Unauthorized in 16ms >> >> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:58 -0400 >> Completed 201 Created in 969ms (Views: 1.1ms | ActiveRecord: 39.6ms) >> >> >> GOOD >> -------------- >> >> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >> Completed 401 Unauthorized in 1ms >> >> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >> Completed 204 No Content in 153ms (Views: 2.1ms | ActiveRecord: 3.4ms) >> >> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >> Completed 401 Unauthorized in 4ms >> >> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >> Completed 201 Created in 591ms (Views: 1.2ms | ActiveRecord: 58.8ms) >> >> >> So it seems there are two extra requests, one HEAD and one POST that >> are made at the beginning of the bad chain. I have no idea why. Any >> ideas? Am I returning the right things here? It seems like a bit of a >> bummer that the app is making two post requests even when it works, >> but maybe this is how Basic authentication works? I'm not sure... >> >

I suspect it wouldn't but I will try. Perhaps I could see what the
chain of requests is through logcat and compare it to my own. When
does Carl get back?

··· On 27 July 2011 03:56, Yaw Anokwa wrote: > carl's the most familiar with the networking code and he's in india on > a deployment. it's going to take some time before he can track this > down. in the meanwhile, does any of this happen if you try it against > an app engine instance with auth? > > On Tue, Jul 26, 2011 at 12:51, Thomas Smyth wrote: >> Anyone? >> >> On 25 July 2011 12:17, Thomas Smyth wrote: >>> So I have some more insight on this. It seems to only happen during >>> sends when the authentication box pops up. So for example, the first >>> send since the app is started. I assume this box pops up because the >>> credentials have yet to be saved in the http session. >>> >>> Anyway, I looked at the requests and responses when the box stays up >>> and when it goes away properly. Here's what I'm seeing. (Keep in mind >>> this is a custom aggregator so the problem could be in the way I'm >>> handling the requests.) >>> >>> >>> BAD >>> ----------- >>> >>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:51 -0400 >>> Completed 401 Unauthorized in 1ms >>> >>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:52 -0400 >>> Completed 401 Unauthorized in 60ms >>> >>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>> Completed 401 Unauthorized in 1ms >>> >>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>> Completed 204 No Content in 170ms (Views: 36.0ms | ActiveRecord: 2.4ms) >>> >>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>> Completed 401 Unauthorized in 16ms >>> >>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:58 -0400 >>> Completed 201 Created in 969ms (Views: 1.1ms | ActiveRecord: 39.6ms) >>> >>> >>> GOOD >>> -------------- >>> >>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >>> Completed 401 Unauthorized in 1ms >>> >>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >>> Completed 204 No Content in 153ms (Views: 2.1ms | ActiveRecord: 3.4ms) >>> >>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >>> Completed 401 Unauthorized in 4ms >>> >>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >>> Completed 201 Created in 591ms (Views: 1.2ms | ActiveRecord: 58.8ms) >>> >>> >>> So it seems there are two extra requests, one HEAD and one POST that >>> are made at the beginning of the bad chain. I have no idea why. Any >>> ideas? Am I returning the right things here? It seems like a bit of a >>> bummer that the app is making two post requests even when it works, >>> but maybe this is how Basic authentication works? I'm not sure... >>> >> >

I have fixed this. How do I submit a patch? I have opened the issue as
well, so that I can close it once I submit the patch.

I also found another bug and have opened an issue for that and also
know how to fix it.

Please advise.

··· On 27 July 2011 08:27, Thomas Smyth wrote: > I suspect it wouldn't but I will try. Perhaps I could see what the > chain of requests is through logcat and compare it to my own. When > does Carl get back? > > On 27 July 2011 03:56, Yaw Anokwa wrote: >> carl's the most familiar with the networking code and he's in india on >> a deployment. it's going to take some time before he can track this >> down. in the meanwhile, does any of this happen if you try it against >> an app engine instance with auth? >> >> On Tue, Jul 26, 2011 at 12:51, Thomas Smyth wrote: >>> Anyone? >>> >>> On 25 July 2011 12:17, Thomas Smyth wrote: >>>> So I have some more insight on this. It seems to only happen during >>>> sends when the authentication box pops up. So for example, the first >>>> send since the app is started. I assume this box pops up because the >>>> credentials have yet to be saved in the http session. >>>> >>>> Anyway, I looked at the requests and responses when the box stays up >>>> and when it goes away properly. Here's what I'm seeing. (Keep in mind >>>> this is a custom aggregator so the problem could be in the way I'm >>>> handling the requests.) >>>> >>>> >>>> BAD >>>> ----------- >>>> >>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:51 -0400 >>>> Completed 401 Unauthorized in 1ms >>>> >>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:52 -0400 >>>> Completed 401 Unauthorized in 60ms >>>> >>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>> Completed 401 Unauthorized in 1ms >>>> >>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>> Completed 204 No Content in 170ms (Views: 36.0ms | ActiveRecord: 2.4ms) >>>> >>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>> Completed 401 Unauthorized in 16ms >>>> >>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:58 -0400 >>>> Completed 201 Created in 969ms (Views: 1.1ms | ActiveRecord: 39.6ms) >>>> >>>> >>>> GOOD >>>> -------------- >>>> >>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >>>> Completed 401 Unauthorized in 1ms >>>> >>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >>>> Completed 204 No Content in 153ms (Views: 2.1ms | ActiveRecord: 3.4ms) >>>> >>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >>>> Completed 401 Unauthorized in 4ms >>>> >>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >>>> Completed 201 Created in 591ms (Views: 1.2ms | ActiveRecord: 58.8ms) >>>> >>>> >>>> So it seems there are two extra requests, one HEAD and one POST that >>>> are made at the beginning of the bad chain. I have no idea why. Any >>>> ideas? Am I returning the right things here? It seems like a bit of a >>>> bummer that the app is making two post requests even when it works, >>>> but maybe this is how Basic authentication works? I'm not sure... >>>> >>> >> >

Our ideal approach to submitting a patch is to clone the collect
repository on google code, this will create another collect repository
on google code that we can access. The button to do this is located at
the following link:
http://code.google.com/p/opendatakit/source/checkout?repo=collect

Once your changes are ready for review and pushing into the ODK code
base file an issue with a link to cloned repository and a description
of what you changed. Some one will review it and integrate your
changes into the ODK collect code base.

Cheers,
Waylon

··· On Wed, Jul 27, 2011 at 8:26 AM, Thomas Smyth wrote: > I have fixed this. How do I submit a patch? I have opened the issue as > well, so that I can close it once I submit the patch. > > I also found another bug and have opened an issue for that and also > know how to fix it. > > Please advise. > > On 27 July 2011 08:27, Thomas Smyth wrote: >> I suspect it wouldn't but I will try. Perhaps I could see what the >> chain of requests is through logcat and compare it to my own. When >> does Carl get back? >> >> On 27 July 2011 03:56, Yaw Anokwa wrote: >>> carl's the most familiar with the networking code and he's in india on >>> a deployment. it's going to take some time before he can track this >>> down. in the meanwhile, does any of this happen if you try it against >>> an app engine instance with auth? >>> >>> On Tue, Jul 26, 2011 at 12:51, Thomas Smyth wrote: >>>> Anyone? >>>> >>>> On 25 July 2011 12:17, Thomas Smyth wrote: >>>>> So I have some more insight on this. It seems to only happen during >>>>> sends when the authentication box pops up. So for example, the first >>>>> send since the app is started. I assume this box pops up because the >>>>> credentials have yet to be saved in the http session. >>>>> >>>>> Anyway, I looked at the requests and responses when the box stays up >>>>> and when it goes away properly. Here's what I'm seeing. (Keep in mind >>>>> this is a custom aggregator so the problem could be in the way I'm >>>>> handling the requests.) >>>>> >>>>> >>>>> BAD >>>>> ----------- >>>>> >>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:51 -0400 >>>>> Completed 401 Unauthorized in 1ms >>>>> >>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:52 -0400 >>>>> Completed 401 Unauthorized in 60ms >>>>> >>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>>> Completed 401 Unauthorized in 1ms >>>>> >>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>>> Completed 204 No Content in 170ms (Views: 36.0ms | ActiveRecord: 2.4ms) >>>>> >>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>>> Completed 401 Unauthorized in 16ms >>>>> >>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:58 -0400 >>>>> Completed 201 Created in 969ms (Views: 1.1ms | ActiveRecord: 39.6ms) >>>>> >>>>> >>>>> GOOD >>>>> -------------- >>>>> >>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >>>>> Completed 401 Unauthorized in 1ms >>>>> >>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >>>>> Completed 204 No Content in 153ms (Views: 2.1ms | ActiveRecord: 3.4ms) >>>>> >>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >>>>> Completed 401 Unauthorized in 4ms >>>>> >>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >>>>> Completed 201 Created in 591ms (Views: 1.2ms | ActiveRecord: 58.8ms) >>>>> >>>>> >>>>> So it seems there are two extra requests, one HEAD and one POST that >>>>> are made at the beginning of the bad chain. I have no idea why. Any >>>>> ideas? Am I returning the right things here? It seems like a bit of a >>>>> bummer that the app is making two post requests even when it works, >>>>> but maybe this is how Basic authentication works? I'm not sure... >>>>> >>>> >>> >> >

If I have two patches (I do) should I put them both in the same cloned
repo and then just make clear in the commit log which commit is for
which?

··· On 27 July 2011 15:29, W. Brunette wrote: > Our ideal approach to submitting a patch is to clone the collect > repository on google code, this will create another collect repository > on google code that we can access. The button to do this is located at > the following link: > http://code.google.com/p/opendatakit/source/checkout?repo=collect > > Once your changes are ready for review and pushing into the ODK code > base file an issue with a link to cloned repository and a description > of what you changed. Some one will review it and integrate your > changes into the ODK collect code base. > > Cheers, > Waylon > > On Wed, Jul 27, 2011 at 8:26 AM, Thomas Smyth wrote: >> I have fixed this. How do I submit a patch? I have opened the issue as >> well, so that I can close it once I submit the patch. >> >> I also found another bug and have opened an issue for that and also >> know how to fix it. >> >> Please advise. >> >> On 27 July 2011 08:27, Thomas Smyth wrote: >>> I suspect it wouldn't but I will try. Perhaps I could see what the >>> chain of requests is through logcat and compare it to my own. When >>> does Carl get back? >>> >>> On 27 July 2011 03:56, Yaw Anokwa wrote: >>>> carl's the most familiar with the networking code and he's in india on >>>> a deployment. it's going to take some time before he can track this >>>> down. in the meanwhile, does any of this happen if you try it against >>>> an app engine instance with auth? >>>> >>>> On Tue, Jul 26, 2011 at 12:51, Thomas Smyth wrote: >>>>> Anyone? >>>>> >>>>> On 25 July 2011 12:17, Thomas Smyth wrote: >>>>>> So I have some more insight on this. It seems to only happen during >>>>>> sends when the authentication box pops up. So for example, the first >>>>>> send since the app is started. I assume this box pops up because the >>>>>> credentials have yet to be saved in the http session. >>>>>> >>>>>> Anyway, I looked at the requests and responses when the box stays up >>>>>> and when it goes away properly. Here's what I'm seeing. (Keep in mind >>>>>> this is a custom aggregator so the problem could be in the way I'm >>>>>> handling the requests.) >>>>>> >>>>>> >>>>>> BAD >>>>>> ----------- >>>>>> >>>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:51 -0400 >>>>>> Completed 401 Unauthorized in 1ms >>>>>> >>>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:52 -0400 >>>>>> Completed 401 Unauthorized in 60ms >>>>>> >>>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>>>> Completed 401 Unauthorized in 1ms >>>>>> >>>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>>>> Completed 204 No Content in 170ms (Views: 36.0ms | ActiveRecord: 2.4ms) >>>>>> >>>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>>>> Completed 401 Unauthorized in 16ms >>>>>> >>>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:58 -0400 >>>>>> Completed 201 Created in 969ms (Views: 1.1ms | ActiveRecord: 39.6ms) >>>>>> >>>>>> >>>>>> GOOD >>>>>> -------------- >>>>>> >>>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >>>>>> Completed 401 Unauthorized in 1ms >>>>>> >>>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >>>>>> Completed 204 No Content in 153ms (Views: 2.1ms | ActiveRecord: 3.4ms) >>>>>> >>>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >>>>>> Completed 401 Unauthorized in 4ms >>>>>> >>>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >>>>>> Completed 201 Created in 591ms (Views: 1.2ms | ActiveRecord: 58.8ms) >>>>>> >>>>>> >>>>>> So it seems there are two extra requests, one HEAD and one POST that >>>>>> are made at the beginning of the bad chain. I have no idea why. Any >>>>>> ideas? Am I returning the right things here? It seems like a bit of a >>>>>> bummer that the app is making two post requests even when it works, >>>>>> but maybe this is how Basic authentication works? I'm not sure... >>>>>> >>>>> >>>> >>> >> >

That sounds reasonable.

Waylon

··· On Wed, Jul 27, 2011 at 1:25 PM, Thomas Smyth wrote: > If I have two patches (I do) should I put them both in the same cloned > repo and then just make clear in the commit log which commit is for > which? > > On 27 July 2011 15:29, W. Brunette wrote: >> Our ideal approach to submitting a patch is to clone the collect >> repository on google code, this will create another collect repository >> on google code that we can access. The button to do this is located at >> the following link: >> http://code.google.com/p/opendatakit/source/checkout?repo=collect >> >> Once your changes are ready for review and pushing into the ODK code >> base file an issue with a link to cloned repository and a description >> of what you changed. Some one will review it and integrate your >> changes into the ODK collect code base. >> >> Cheers, >> Waylon >> >> On Wed, Jul 27, 2011 at 8:26 AM, Thomas Smyth wrote: >>> I have fixed this. How do I submit a patch? I have opened the issue as >>> well, so that I can close it once I submit the patch. >>> >>> I also found another bug and have opened an issue for that and also >>> know how to fix it. >>> >>> Please advise. >>> >>> On 27 July 2011 08:27, Thomas Smyth wrote: >>>> I suspect it wouldn't but I will try. Perhaps I could see what the >>>> chain of requests is through logcat and compare it to my own. When >>>> does Carl get back? >>>> >>>> On 27 July 2011 03:56, Yaw Anokwa wrote: >>>>> carl's the most familiar with the networking code and he's in india on >>>>> a deployment. it's going to take some time before he can track this >>>>> down. in the meanwhile, does any of this happen if you try it against >>>>> an app engine instance with auth? >>>>> >>>>> On Tue, Jul 26, 2011 at 12:51, Thomas Smyth wrote: >>>>>> Anyone? >>>>>> >>>>>> On 25 July 2011 12:17, Thomas Smyth wrote: >>>>>>> So I have some more insight on this. It seems to only happen during >>>>>>> sends when the authentication box pops up. So for example, the first >>>>>>> send since the app is started. I assume this box pops up because the >>>>>>> credentials have yet to be saved in the http session. >>>>>>> >>>>>>> Anyway, I looked at the requests and responses when the box stays up >>>>>>> and when it goes away properly. Here's what I'm seeing. (Keep in mind >>>>>>> this is a custom aggregator so the problem could be in the way I'm >>>>>>> handling the requests.) >>>>>>> >>>>>>> >>>>>>> BAD >>>>>>> ----------- >>>>>>> >>>>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:51 -0400 >>>>>>> Completed 401 Unauthorized in 1ms >>>>>>> >>>>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:52 -0400 >>>>>>> Completed 401 Unauthorized in 60ms >>>>>>> >>>>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>>>>> Completed 401 Unauthorized in 1ms >>>>>>> >>>>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>>>>> Completed 204 No Content in 170ms (Views: 36.0ms | ActiveRecord: 2.4ms) >>>>>>> >>>>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:57 -0400 >>>>>>> Completed 401 Unauthorized in 16ms >>>>>>> >>>>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:04:58 -0400 >>>>>>> Completed 201 Created in 969ms (Views: 1.1ms | ActiveRecord: 39.6ms) >>>>>>> >>>>>>> >>>>>>> GOOD >>>>>>> -------------- >>>>>>> >>>>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >>>>>>> Completed 401 Unauthorized in 1ms >>>>>>> >>>>>>> Started HEAD "/submission" for 10.1.0.202 at 2011-07-25 12:05:47 -0400 >>>>>>> Completed 204 No Content in 153ms (Views: 2.1ms | ActiveRecord: 3.4ms) >>>>>>> >>>>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >>>>>>> Completed 401 Unauthorized in 4ms >>>>>>> >>>>>>> Started POST "/submission" for 10.1.0.202 at 2011-07-25 12:05:48 -0400 >>>>>>> Completed 201 Created in 591ms (Views: 1.2ms | ActiveRecord: 58.8ms) >>>>>>> >>>>>>> >>>>>>> So it seems there are two extra requests, one HEAD and one POST that >>>>>>> are made at the beginning of the bad chain. I have no idea why. Any >>>>>>> ideas? Am I returning the right things here? It seems like a bit of a >>>>>>> bummer that the app is making two post requests even when it works, >>>>>>> but maybe this is how Basic authentication works? I'm not sure... >>>>>>> >>>>>> >>>>> >>>> >>> >> >