Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
We are using bakery. When attempting to log in this evening the browser returned this below. This occurred half a dozen times on different machines within the same internal network. The /admin/reports/ provided no clues. Has anyone ever seen anything like this? Clues as to what it might mean?
Comment | File | Size | Author |
---|---|---|---|
bakery_strangeness.png | 234.42 KB | stefanwray |
Comments
Comment #1
coltraneI haven't seen this. Did you get this after any changes you made to your site?
Have you tried clearing the cache?
Comment #2
tunicAlmost four months with no feedback, postponed.
Comment #3
solotandem CreditAttribution: solotandem commentedIn my tests of the login workflow, I have found two "consistent" patterns of undesirable results due to what I will call "missing cookies on the master site." I have seen this behavior with FireFox, and others with Safari, and possibly Chrome. The behavior seems not due to bakery code but to "corruption" in the $_COOKIE array, which cause may be a browser bug.
If you can reproduce the condition of:
- $_COOKIE on master does not contain the CHOCOLATECHIP cookie when trying to login on slave
then:
- go to /user/login on slave
- if user is NOT logged into master site
-- then garbage is returned as drupal renders bakery/login which outputs user/login (see screenshot in Issue Summary)
- if user is logged into master site
-- seems to require root user (see this comment on #1945936: Access denied to /bakery/login after logged out from slave when still logged in to master)
-- then redirect loop occurs because authenticated user on master fails the user_is_anonymous() access check for bakery/login
Comment #4
coltrane@solotandem are you testing on a system that's using any front-end proxy or similar that might strip certain elements out of request headers?
Comment #5
solotandem CreditAttribution: solotandem commentedNo front-end proxy.
The "garbage" returned behavior is infrequent and its cause unknown. My guesses include:
- cache clearing on one site but not the other
- browser issues
The redirect loop is consistent but only I have only seen it occur when you first login as root user, then logout of slave (leaving root logged in on master) and re-login as non-root user on slave. This will happen every time.
Comment #6
Jim Kirkpatrick CreditAttribution: Jim Kirkpatrick commentedWe've seen this, it's happened for us when we tried to go to /bakery/login (I *think*, it was a while back) when the "Cache pages for anonymous users" PLUS "Compress cached pages" were both enabled in Config -> Development -> Performance.
The garbled response in the screenshot above is in fact the browser's best attempt at rendering a page that Drupal returns from its cache that has been double-gzipped.
The workaround for us was to turn off caching or compression, but this error only occurred on Bakery pages -- our site is for logged-in users only, so this workaround was not a problem for us, but it isn't sensible on busy 'normal' sites.
Marking active too...
Comment #7
randallknutson CreditAttribution: randallknutson commentedWe've been seeing this as well. We have a similar setup as described in #6. Clearing cache on the master site seems to fix the issue temporarily. I just disabled "Compress cached pages" to see if this stops this from occurring in the future.