is this a problem? re - mod rewrite
hm. i have it, but its not enabled by the looks of it. wouldn't I be seeing a lot more errors by now if this wasn't working on my site?
-
If the page is displayed correctly, you can ignore this error
-
also, this is separate but interesting.
-
everything is displayed correctly, but i have some super long load times...as reported by profiler, both for me and for users.
between 13s-54s ....
and the server is sitting on at least 200MBPS of pipe and has a gigabit card.. so bottleneck is not the server delivery ability,
what i wonder is if because mod_rewrite is "undefined" each page request is being called first through the user, then to mod_rewrite in .htaccess, and after running chain, then una says okay well, that didn't work, but we will serve you the page we have, and then una rewrites all the urls dynamically each time to adjust for this error...
this would be solved by ??? and when solved, page loads should be more instantaneous i would believe.. someone correct me here if i am wrong, or perhaps what to look at inside mod_rewrite areas
-
also, this is separate but interesting.
I can see exact same error in our upgrade_modules.log....
-
Mayki , have you figured this one out yet? Mine is still pushing this notice once a day.
-
mode_rewrite couldn't be identified sometimes, so it's ok to ignore UNDEFINED message in server audit.
Long page open is ok if it's for storage files, since it could be big file.
-
I have just been in touch with my rack provider, and they enabled mod_rewrite. I still see the following in audit, but i also had two spaces between the regex and storage in my htaccess file, so that has been corrected.
for the first time finally a user can log in without having to click the three horizonal bars, and then home.. the site finally redirects the user into my una site. which.. has been a great problem for most users who don't understand why they still see the splash when they've already logged in.
So, I feel it is working now, but on an important point to mention the following:
Web-server: Apache
- rewrite_module - UNDEFINED (try to check manually: apachectl -M 2>&1 | grep rewrite_module)
is how i see in server audit. however it is there as rewrite. perhaps a line or two in the wiki documentation can be added to assist people in verifying the module manually, in cases where theirs is not named rewrite_module, and they uses apache2... ie: apache2ctl -M 2>&1 | grep rewrite
