This could be related to
#6034

Hi, tested #6542 and although the redirected page looks better, the url is stil wrong:
e.g. on another site it redirects to: https://mydomain/blog-overzicht?view=categories
where it should redirect to https://mydomain/blog-overzicht

Confirmed, I also see a difference in the menu item link. With Testdata I have

in 3.4.0
Home == "index.php"

in 3.4.1
Home == "index.php?option=com_content&view=article&id=24&Itemid=435"

@Hackwar looks like a routing issue (although not certain by any means on that)

revert #6034 doesn't solve this problem, it seems that the change (problem) is the home URL. It redirects to the home page and that is usually "index.php" or "/". For the test data that is the same as "index.php?option=com_content&view=article&id=24&Itemid=435" because that is the link behind it. So as I said

in 3.4.0
Home == "index.php"

in 3.4.1
Home == "index.php?option=com_content&view=article&id=24&Itemid=435"

it is a changed behaviour of JRoute for the home page

Test Data
Itemid=435 is the homepage

JRoute::_('index.php&Itemid=435');

for 3.4.0 it returns "index.php"
and for 3.4.1 it returns "index.php?option=com_content&view=article&id=24&Itemid=435"

it's not 'limited' to the homepage but to every menu entry that you redirect to:
I have a menu 'blog-overzicht' that logout redirects to, so my url should be [mydomain]/blog-overzicht but it redirects to [mydomain]/component/cjblog/?view=categories

Since our update to Joomla! 3.4.1 we do have the same issue like Ruud68. In our case both redirections, the login as well as the logout, are not working correct. Today I have installed the VTEM Login-module, but no change.

Having the same issue, but with login redirect. It directs to the long form URL, and not the SEF URL like it did in version 3.4.0 and previous. Are versions tested before they are released?

Having same issue as cogfactory. Both login and logout redirects wrong with Joomla! 3.4.1. Worked ok with 3.4.0.

@cogfactory yes, releases are being tested. However, with several thousand files and most likely infinite combinations of features and settings, not everything can be tested 100%.

I was the one that rewrote the helper of mod_login here #6034 and for some of this issue I have to take the blame. However I also have to say that I actually thought that this would be merged into 3.5 and not into a patch release. Looking at the code, I think #6542 should fix the problem. Please test if that solves your issue.

@Hackwar Yes, #6542 fixed my issues on a production site. i.e. Both login and logout redirects. Thanks.

@Hackwar Will 6542 disrupt a live website?

@cogfactory no. But you should know how to apply such a patch.

Hi, another use case where it is going wrong:
I have a menu item: Titel / kantelingsalfabet that is a menu item alias for menu entry 'kantelingsalfabet' that displays a 'category blog'

the reason I want this is for seo purposes: I do not want the url to be [mydomain]/titel/kantelingsalfabet but [mydomain]/kantelingalfabet.

Works like a charm :)

but. when I set the logout redirect (for testing) to the menu item 'Titel / kantelingsalfabet' It redirects me to [mydomain]/?Itemid=

when I set the redirect to menu entry that is the actual blog category, then I get really unexpected behaviour.
the redirect url = [mydomain]/in-het-nieuws/24-titels/het-kantelingsalfabet
the 'in-het-nieuws' was the menu entry I was on when I pressed logout: so it constructs an redirect url of where I was with where i should be going to.....

So definitely something wrong...

Menu item alias menu items (what a cool name) are not able to route anywhere. They are an alias, not another menu item. So creating a menu item alias with title "kantelingsalfabet" will not create a url /kantelingsalfabet. Otherwise we would have the duplicate content issue that we are actually trying to avoid with the menu item alias.

Regarding your other problem: Do you get that behavior when #6542 is applied to that site?

response in #6542 :)

#6542 Solved my issue. Thank you for your input and support. Joomla rocks!

Since I am a Joomla user only and not familiar with the application of patches, can I expect the issue being solved with Joomla 3.4.2?

We merge the patches as soon as we have two positive tests on an issue. Assuming we get these tests then yes it will be solved in 3.4.2.

Thank You!

see:
#6542 (comment)

for the right code to test

fix in here: #6542 (comment) tested and can confirm that this is working correctly