I did use -I but it did not show any redirects. Anyway, I still don't know why it gets redirected to profile when it is not properly defined.
On Mar 8, 5:25 pm, Jonathan Lundell <[email protected]> wrote: > On Mar 8, 2011, at 2:20 PM, Jonathan Lundell wrote: > > > > > On Mar 8, 2011, at 2:00 PM, DenesL wrote: > > >> I mean curl --trace-ascii > > >> On Mar 8, 4:37 pm, DenesL <[email protected]> wrote: > >>> On Mar 8, 1:06 pm, Jonathan Lundell <[email protected]> wrote: > > >>>> Try making the requests with curl -I and see if there's a chain of > >>>> redirects that might offer a clue. > > >>> Maybe you meant curl -1 (minus one), > >>> using this option I get the default layout with the two forms, no > >>> redirection (?). > > > Just curl -I should show you any redirects. If curl is following the > > redirects (I don't think it does by default) you can use --max-redirs 1. > > For example, I have the stock welcome app deployed at GAE. Here's a sample > curl request that results in a redirect: > > ~ $ curl -Ihttp://jkl-web2py-welcome.appspot.com/welcome/default/user > HTTP/1.1 303 See Other > Set-Cookie: session_id_welcome="3002:826f594f-996f-4e22-9026-81b62e34ff57"; > Path=/ > Content-Type: text/html; charset=UTF-8 > Location: /welcome/default/user/login > Date: Tue, 08 Mar 2011 22:22:38 GMT > Server: Google Frontend > Cache-Control: private, x-gzip-ok="" > Transfer-Encoding: chunked > > Notice that curl doesn't follow the redirect; I think you have to use > --location for that to happen.
