From: Ed Tanous <ed@tanous.net>
To: Mike Jones <proclivis@gmail.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Infinite redirect.
Date: Mon, 27 Jul 2020 12:09:17 -0700 [thread overview]
Message-ID: <CACWQX81_jq5asAMmiU-WCN1xsUDUpGL9DQtw5MuKSiq2q5GEPQ@mail.gmail.com> (raw)
In-Reply-To: <E38290F8-4FC6-4FF3-9FF2-5ED7853FE1DB@gmail.com>
On Mon, Jul 27, 2020 at 12:03 PM Mike Jones <proclivis@gmail.com> wrote:
>
> I need help debugging an infinite redirect.
Without reading the rest of your email, there is a 95% chance that
this means you didn't include phosphor-webui component in your build.
It is a known "bug" that has bit several people, and I've been meaning
to fix it so it at least gives you some better error and/or at least
doesn't redirect, but architecturally it breaks some weird boundaries
a little bit (the login routes have to be aware of which other routes
have been registered, which imposes an unintended ordering on the
route handler) , and I've just never had the chance.
>
> Using tag 2.8.0
>
> I built meta-phosphor with raspberrypi4. See https://github.com/Proclivis/conf-meta-rasberrypi-evb.git
>
> I setup a host entry on my ubuntu laptop in /etc/hosts
>
> 10.0.1.72 bmc
>
> Then with firefox use url
>
> https://bmc:18080
>
> I get a redirect to
>
> https://bmc:18080/#/login?next=%2F
>
> Which also redirects again.
>
> bmcweb is not sending a cookie on the first request.
Nor should it. You're not logged in yet, nor have you given valid
login credentials. The redirect is trying to move you to the webui,
which can then present a pretty login screen. Unfortunately the webui
doesn't exist, so you hit another redirect.
>
> On the target, token_authorization_middleware.hpp:187 is failing the cookie authorization, probably because Firefox is not sending back the cookie it never received.
>
> There are two failed services not running:
>
> obmc-phosphor-sysd.service
> start-ipkvm-.service
Those should be irrelevant to this issue.
>
> I assume these would not interfere with something as basic as cookies.
>
> Is there something I need to configure on the target?
See above.
next prev parent reply other threads:[~2020-07-27 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 19:01 Infinite redirect Mike Jones
2020-07-27 19:09 ` Ed Tanous [this message]
2020-07-27 23:06 ` Mike
2020-07-27 23:11 ` Ed Tanous
2020-07-27 23:27 ` Mike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACWQX81_jq5asAMmiU-WCN1xsUDUpGL9DQtw5MuKSiq2q5GEPQ@mail.gmail.com \
--to=ed@tanous.net \
--cc=openbmc@lists.ozlabs.org \
--cc=proclivis@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.