Hi,
I am using the single signon module on multiple sites. The sites are subdomains of beiruter.com so i have news.beiruter.com directory.beiruter.com etc..
I am having a problem with the feeds of the slave site. In the browser, it loads fine.. but aggregators and feedvalidator return an error:
Server returned HTTP Error 302: The HTTP server returned a redirect error that would lead to an infinite loop.
The error disappears when i deactivate the singlesignon module.. i think it has something to do with cookies..
One solution would be to disable singlesignon for feeds, i can't see the utility of the module there.. but dunno if it's doable..
Anyho,
here's what feedvalidator says for the feed of the slave site:
http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fdirectory.beiruter.c...
for the master site it works, check it here:
http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fnews.beiruter.com%2F...
Any ideas how to solve this?
Comments
Comment #1
zis commentedanyone here?
PS: the examples i posted above won't work anymore because i disabled single signon..
Comment #2
danielc commentedSorry for the delay. The "charming" bug system didn't send me an email when you initially posted. I don't have an immediate solution for you nor the time at the moment to come up with one. Perhaps you can come up with a patch?
Comment #3
danielc commentedComment #4
Anonymous (not verified) commentedThis is still appearing on 5.1 sites.
We have two sites sharing the same code, but with different themes etc. Same errors as previously noted.
Comment #5
aspankie commentedHey guys. Please see the fix I used here to get my RSS feeds for my slave sites working: http://drupal.org/node/112996 Works great!
Comment #6
aspankie commentedOr I could make it easy for you and post it here:
Put it at the very top of singlesignon_init() in singlesignon.module
Comment #7
Anonymous (not verified) commentedExcellent! Thanks.
Comment #8
starkos commentedI've posted this a couple of places, but in case someone stumbles through here...I've come up with a fix for this and several related issues. You can get it from my site (with a brief explanation of the fix).
Comment #9
wayland76 commentedThis is a duplicate of http://drupal.org/node/170001 (yes, I know this one's older)