Receiving just error codes when making requests
17 views
Skip to first unread message
Thyako
Sep 22, 2008, 4:00:14 PM9/22/08
to Orkut Developer Forum
I'm tracking the errors being shown in the users' applications and I
am seeing what seems to be orkut's internal errors.
The response from gadgets.io.makeRequest is just an object with the
key 'errors' with value "Error 12029" or more frequently "Error
12152".
Is that fine? What do that means? I'm assuming I cant do nothing to
avoid them.
~Thiago
am seeing what seems to be orkut's internal errors.
The response from gadgets.io.makeRequest is just an object with the
key 'errors' with value "Error 12029" or more frequently "Error
12152".
Is that fine? What do that means? I'm assuming I cant do nothing to
avoid them.
~Thiago
Jason
Sep 23, 2008, 8:07:49 PM9/23/08
to Orkut Developer Forum
Hi Thiago. I need a bit more context. Did you start seeing these
errors recently? Are they sporadic (i.e. do they come and go often)?
You mention "more frequently" -- about how frequent are they? Do they
appear in Internet Explorer only or other browsers?
I came across this page which lists various unusual status codes
including 12029 and 12152, which seems to indicate that the server is
flaky or not connected:
http://wiki.motionbased.com/mb/MotionBased_Agent#HTTP_Status_12029
Are you able to vouch for the health of your network connection?
- Jason
errors recently? Are they sporadic (i.e. do they come and go often)?
You mention "more frequently" -- about how frequent are they? Do they
appear in Internet Explorer only or other browsers?
I came across this page which lists various unusual status codes
including 12029 and 12152, which seems to indicate that the server is
flaky or not connected:
http://wiki.motionbased.com/mb/MotionBased_Agent#HTTP_Status_12029
Are you able to vouch for the health of your network connection?
- Jason
Thyako
Sep 29, 2008, 1:43:20 PM9/29/08
to Orkut Developer Forum
Hi.
Sorry for the delay. We were collecting more data.
Summary: The more frequent error (400 bad request) stopped forever
when we stopped asking gadgets.io.makeRequest for signed requests.
Other errors continue in a low rate.
Details:
- We are using Google AppEngine in server side.
- We tracked user-agent, and the errors occur with all browsers
(IE6-7, FF2-3 and Chrome observed).
- When the app (javascript/client side) does not receive successful
data, it tries the request again twice, and if the error continues it
shows a message to the user and makes another request, to the same
server, but to log the collected data. This last is not signed.
- In our log, we can see that collected data about the error, which
was generated when the user 123 was trying to request "/msgs". But we
can't find, in the request logs, that request of that user asking for
/msgs. This suggests our server is not receiving the request, or that
AppEngine is not logging them.
- I used the application a lot, and got just the 400 error about four
times in different days. When that occured, all subsequent requests
didn't work. It was needed to reload the page (the orkut
Application.aspx), and everything worked fine, suggesting it was like
an orkut authentication token that expired, maybe.
- Besides that all subsequent errors, the requests to log the errors
continues to work! (and are not signed).
- When I got the 400 error, firebug showed the following in the
"responde" tab of the XmlHttpRequest:
<HTML>
<HEAD>
<TITLE>Bad Request</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Bad Request</H1>
<H2>Error 400</H2>
</BODY>
</HTML>
- This may suggest the request didn't reach my server, because if so
firebug would show something like:
throw 1; < don't be evil' >{"http://xx/msgs/":{"headers":
{},"body":"Bad Request Error 400 (...)
Other relevant data:
- First I stopped signature-checking in my server. The 400 errors
continued. Then I stopped asking signed requests in the app and 400
never occurred anymore since last friday, 26th.
- The 400 errors I've got (with my browser) occurred only after
using the application by several minutes and making several requests
(like updating and sending messages).
- The other errors include "Error not specified", "Error 0", "Error
12152", "Error 12007", "Error 502", "Error 12031", and maybe others I
haven't seen in the big log.
- In September 28th, these errors occurred in a frequency like: 6h32,
6h44, 7h4, 7h18, 7h21, 7h27, 7h34, 8h12, 8h34 and with more activity
of users: 8h45,46,49,50,52,54...
- The 400 errors frequency were more high.
- We have an average of ten requests per second in AppEngine.
- Other errors are shown to the user because AppEngine returned real
errors with the request, like timeout to fetch data etc. In this case
the key "errors" in the response object contains "failed to parse
JSON", because my server returned the traceback.
- The application is http://www.orkut.com/Main#AppInfo.aspx?appId=751275171894
What a weird issue... I tried to reproduce it in CodeRunner, making a
loop of signed requests (with a 'nocache' parameter with random value)
to google.com and to my personal data in my application, for 30
minutes, but everything was fine, without errors.
Anyway, there are users receiving errors about this. It's not just
with me. I started tracking errors on users' requests to check unknown
bugs in my code, and the only errors I found was those.
Finally, does anyone else track errors in client side?
~Thiago
Sorry for the delay. We were collecting more data.
Summary: The more frequent error (400 bad request) stopped forever
when we stopped asking gadgets.io.makeRequest for signed requests.
Other errors continue in a low rate.
Details:
- We are using Google AppEngine in server side.
- We tracked user-agent, and the errors occur with all browsers
(IE6-7, FF2-3 and Chrome observed).
- When the app (javascript/client side) does not receive successful
data, it tries the request again twice, and if the error continues it
shows a message to the user and makes another request, to the same
server, but to log the collected data. This last is not signed.
- In our log, we can see that collected data about the error, which
was generated when the user 123 was trying to request "/msgs". But we
can't find, in the request logs, that request of that user asking for
/msgs. This suggests our server is not receiving the request, or that
AppEngine is not logging them.
- I used the application a lot, and got just the 400 error about four
times in different days. When that occured, all subsequent requests
didn't work. It was needed to reload the page (the orkut
Application.aspx), and everything worked fine, suggesting it was like
an orkut authentication token that expired, maybe.
- Besides that all subsequent errors, the requests to log the errors
continues to work! (and are not signed).
- When I got the 400 error, firebug showed the following in the
"responde" tab of the XmlHttpRequest:
<HTML>
<HEAD>
<TITLE>Bad Request</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Bad Request</H1>
<H2>Error 400</H2>
</BODY>
</HTML>
- This may suggest the request didn't reach my server, because if so
firebug would show something like:
throw 1; < don't be evil' >{"http://xx/msgs/":{"headers":
{},"body":"Bad Request Error 400 (...)
Other relevant data:
- First I stopped signature-checking in my server. The 400 errors
continued. Then I stopped asking signed requests in the app and 400
never occurred anymore since last friday, 26th.
- The 400 errors I've got (with my browser) occurred only after
using the application by several minutes and making several requests
(like updating and sending messages).
- The other errors include "Error not specified", "Error 0", "Error
12152", "Error 12007", "Error 502", "Error 12031", and maybe others I
haven't seen in the big log.
- In September 28th, these errors occurred in a frequency like: 6h32,
6h44, 7h4, 7h18, 7h21, 7h27, 7h34, 8h12, 8h34 and with more activity
of users: 8h45,46,49,50,52,54...
- The 400 errors frequency were more high.
- We have an average of ten requests per second in AppEngine.
- Other errors are shown to the user because AppEngine returned real
errors with the request, like timeout to fetch data etc. In this case
the key "errors" in the response object contains "failed to parse
JSON", because my server returned the traceback.
- The application is http://www.orkut.com/Main#AppInfo.aspx?appId=751275171894
What a weird issue... I tried to reproduce it in CodeRunner, making a
loop of signed requests (with a 'nocache' parameter with random value)
to google.com and to my personal data in my application, for 30
minutes, but everything was fine, without errors.
Anyway, there are users receiving errors about this. It's not just
with me. I started tracking errors on users' requests to check unknown
bugs in my code, and the only errors I found was those.
Finally, does anyone else track errors in client side?
~Thiago
Jason
Oct 1, 2008, 2:30:51 PM10/1/08
to Orkut Developer Forum
Hi Thiago. Yes, this may very well indicate an error in our back-end,
judging by the response you provided. Can you set up replica of your
current spec which uses signed requests and provide me the URL? This
will hopefully enable me to reproduce the issue, which should help me
track down the cause a bit quicker. Also, please let me know how to
use your app in order to see the errors.
- Jason
> - The application ishttp://www.orkut.com/Main#AppInfo.aspx?appId=751275171894
judging by the response you provided. Can you set up replica of your
current spec which uses signed requests and provide me the URL? This
will hopefully enable me to reproduce the issue, which should help me
track down the cause a bit quicker. Also, please let me know how to
use your app in order to see the errors.
- Jason
Thyako
Oct 1, 2008, 3:24:12 PM10/1/08
to Orkut Developer Forum
Use http://truthapp.appspot.com/s/orkut_signed_temp.xml (signed
requests in both canvas and profile - but they aren't checked in
server side).
You can post as many "truths" as you wish to me (
http://www.orkut.com/Profile.aspx?uid=15227094260667991002 ) and to
yourself through your profile. Later, click "refresh" to see the
messages without reloading the canvas, and click "reply", too (you can
reply to yourself).
That's how I've got errors, except it was interacting with real people
(which makes more diverse the values of one url parameter, besides the
random no-chache param and the POST data).
Thanks for checking.
~Thiago
requests in both canvas and profile - but they aren't checked in
server side).
You can post as many "truths" as you wish to me (
http://www.orkut.com/Profile.aspx?uid=15227094260667991002 ) and to
yourself through your profile. Later, click "refresh" to see the
messages without reloading the canvas, and click "reply", too (you can
reply to yourself).
That's how I've got errors, except it was interacting with real people
(which makes more diverse the values of one url parameter, besides the
random no-chache param and the POST data).
Thanks for checking.
~Thiago
Jason
Oct 2, 2008, 6:24:44 PM10/2/08
to Orkut Developer Forum
Thanks for posting the replica. I haven't been able to post any
anonymous truths because the profile view isn't loading. Firebug is
reporting that opensocial.DataRequest.PersonId is undefined. It looks
like you might be overwriting the DataRequest object; can you take a
quick look and send a reply when this issue is fixed?
- Jason
On Oct 1, 12:24 pm, Thyako <thy...@gmail.com> wrote:
> Usehttp://truthapp.appspot.com/s/orkut_signed_temp.xml(signed
anonymous truths because the profile view isn't loading. Firebug is
reporting that opensocial.DataRequest.PersonId is undefined. It looks
like you might be overwriting the DataRequest object; can you take a
quick look and send a reply when this issue is fixed?
- Jason
On Oct 1, 12:24 pm, Thyako <thy...@gmail.com> wrote:
> Usehttp://truthapp.appspot.com/s/orkut_signed_temp.xml(signed
> requests in both canvas and profile - but they aren't checked in
> server side).
>
> You can post as many "truths" as you wish to me (http://www.orkut.com/Profile.aspx?uid=15227094260667991002) and to
> server side).
>
Jason
Oct 3, 2008, 2:15:30 PM10/3/08
to Orkut Developer Forum
Never mind, this appears to be a sandbox issue. I'll continue testing
your app in prod.sandbox.orkut.com and will get back to you soon.
- Jason
your app in prod.sandbox.orkut.com and will get back to you soon.
- Jason
Reply all
Reply to author
Forward
0 new messages