Hi there

Thank you for an excellent module.

I recently did the upgrade to 7.x-1.1 and the login to the site stopped working. After a correct login, the user is just redirected to the user login page, no error messages.

I downgraded to 7.x-1.0 and the same issues occurred. After regenerating the .htaccess code using 7.x-1.0 the user login worked again. Reinstalling 7.x-1.1 with the 7.x-1.0 .htaccess code also allowed the user to login.

My server specs are: Server Version: Apache/2.2.31 (Unix) mod_ssl/2.2.31 OpenSSL/1.0.1e-fips mod_bwlimited/1.4 PHP/5.5.30

Best wishes,

Paul

Comments

_paul_meta created an issue. See original summary.

bohus ulrych’s picture

bohus ulrych
Location Pilsen (Czechia)
commented

Hi all,
I have same issue - I was not able to log in.
This scenario is working: Reinstalling 7.x-1.1 with the 7.x-1.0 .htaccess code also allowed the user to login.

antims’s picture

antims commented

Same problem with me,the generated .htaccess code is wrong.

patoshi’s picture

patoshi commented

http://prntscr.com/b8qnym -- comparision of the 1.1 and 1.0 .htaccess code.

I can also confirm that the 1.0 version's htaccess code works on 1.1

The 1.1 generates an incorrect .htaccess code which renders all forms nonfunctioning even in the admin screens.

jorges’s picture

jorges commented

Hi, I had a similar problem and replaced
RewriteRule .* - [S=2]
with
RewriteRule .* - [S=1]

See below in context:

  # Caching for anonymous users
  # Skip boost IF not get request OR uri has wrong dir OR cookie is set OR request came from this server
  RewriteCond %{REQUEST_METHOD} !^(GET|HEAD)$ [OR]
  RewriteCond %{REQUEST_URI} (^/(admin|cache|misc|modules|sites|system|openid|themes|node/add|comment/reply))|(/(edit|user|user/(login|password|register))$)  [OR]
  RewriteCond %{HTTP_COOKIE} DRUPAL_UID [OR]
  RewriteCond %{ENV:REDIRECT_STATUS} 200

  # This original line from Boost is probably wrong
  # Replaced it with the line below.
  # RewriteRule .* - [S=2]
  RewriteRule .* - [S=1]

#  # Apache 2.4 bug workaround
#  # Enables caching of index/ home page
#  RewriteCond %{REQUEST_URI} ^/index\.php$
#  RewriteCond %{DOCUMENT_ROOT}/cache/%{ENV:boostpath}/%{HTTP_HOST}/\_%{QUERY_STRING}\.html -s
#  RewriteRule .* cache/%{ENV:boostpath}/%{HTTP_HOST}/\_%{QUERY_STRING}\.html [L,T=text/html]

  # NORMAL
  RewriteCond %{DOCUMENT_ROOT}/cache/%{ENV:boostpath}/%{HTTP_HOST}%{REQUEST_URI}_%{QUERY_STRING}\.html -s
  RewriteRule .* cache/%{ENV:boostpath}/%{HTTP_HOST}%{REQUEST_URI}_%{QUERY_STRING}\.html [L,T=text/html]
marcoka’s picture

marcoka commented

i had the same problem too. i just copied over the htaccess code from 1.0
in my case it wasnt especially to the login. it was for like all forms.

Andrew Gorokhovets’s picture

Andrew Gorokhovets commented

Jorges comment (#5) fixed this issue in my case. Thank you!

tamnv’s picture

tamnv commented

#5 worked for me, thanks you!!!

oschuetze’s picture

oschuetze commented

#5 is the solution. Thank you!

philsward’s picture

philsward commented
Related issues: +#2814113: Fix anonymous caching incorrect increment of RewriteRule Skip
bellagio’s picture

bellagio commented

in my case, #5 solves login problem, but cached pages are not served.

aitala’s picture

aitala commented

I have had various solutions work / not work. I think it really depends on the specific version of Apache / Linux and any patches made by the system administrators.

On a server with Apache 2.4.6 on Centos 7.1.1503, I have not been able to get Boost 7.x-1.1 or later to work no matter what I attempt. Either caching fails, search fails, or logins fail. I think the admins applied a patch to address one of the issues with Apache 2.4 which is fixed later, but the patch seems to break whatever fix I add into .htaccess .

I have another site on Apache/2.2.31 on Centos 6.7 running Boost 7.x-1.2 with no problem as far as I can tell.

So.....

Eric

ThirtyOne34’s picture

ThirtyOne34 commented

#5 saved me too.

aniket.mohite88’s picture

aniket.mohite88 commented

#5 worked for me as well. Thanks.

Using boost 7.x-1.2 & Drupal 7.50

nor sairi’s picture

nor sairi commented

#5 is run perfect

adamevertsson’s picture

adamevertsson commented

#5 solved two problems for me: I couldn't log in and the pager always served the first page. Changing a 2 to a 1 solves this.

Could we get an explanation what the 2 and 1 stands for? Could there be any complications for changing this?

philsward’s picture

philsward commented

@AdamEvertsson

The line RewriteRule .* - [S=1] means "skip x number of rules below this line"

So, if S=2, there should be 2 rules below it to skip. If the number doesn't match the actual number of rules, or if the next live rule that isn't skipped doesn't do anything productive, then the rewrite goes all goofy.

Oh, as far as complications go, technically no? But some folks have run into weird issues depending on their setup.

Long story short, the template that was supplied with the latest stables, is incorrect. It's expecting the commented lines to be uncommented to make the line correct. In reality, the commented lines shouldn't really be commented, or the s= line should properly reflect the commented lines with an explanation that "if you uncommented the line, you should change s=1 to s=2.

In a perfect world, the template generator would be setup to output a template for Apache 2.2 and another template for 2.4 so all of this confusion would be eliminated and boost would actually work out-of-the-box.