Hi Jeff, Nick Seems like I posted this stuff twice (another thread I posted was talking about the same thing and answered by Nick). here's the detail 1. size of header: urlencoded header size was 700 bytes more or less, it's a delegation token retrived from live services 2. full url is "https://livecontacts.services.live.com/users/ @l...@3b7beba24ed0d0a4/rest/livecontacts/owner“, which is a normal https url it's a outgoing request (send from appengine to outside), use java runtime thanks ! Michael
On 7月30日, 上午7时51分, "Jeff S (Google)" <j...@google.com> wrote: > Hi Michael, > > Hmmm, the Authorization header should be allowed. There could be a few > factors involved that I'd like to learn a bit more about. What are the > approximate sizes of the authorization header, the full request. Could you > share some of the URLs which these requests are being sent to? Also are > these requests being made to App Engine, or from App Engine (using > URLFetch)? > > Thank you, > > Jeff > > > > On Tue, Jul 28, 2009 at 8:53 PM, Millton <easywo...@gmail.com> wrote: > > > hi all > > I'm currently using the GAE java runtime, and when I compose a > > https request, try to set "Authorization" header, it will be filtered > > by GAE, which caused 401 error all the time, the Authorization header > > is a little longer than basic web auth info, it's used for live > > contacts REST API. > > > so is there any solution or workarround to avoid the limitation? > > thanks! > > Michael- 隐藏被引用文字 - > > - 显示引用的文字 - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
