Ceon URI Mapping v4.x

[mc12345678]

Hi,

I was about to install CEON URI into a zc155e and came here to confirm there were no conflicts. I read thru the conversation about breadcrumb issues and would prefer to avoid them.

I have two questions. First, both Torvista and MC supply github links... which should I use?

Second, Torvista's version is updated for php7 but I'm still running v5.5.38. Am I out of luck or is the php 7 version backwards compatible?

I would suggest torvista's version for now as I created one just to push a change and to carry a conversation.

As for changes to support php 7, changes that have generally been made/needed to support php 7 are conditions that have existed for php 5.x but had not been implemented because they weren't required then. So, you should generally be okay with php 5.5.x and software that supports php 7.

I haven't looked yet, but torvista indicated that he carried over the change we discussed about breadcrumbs. I took his word for it in his previous post indicating that he updated the repo.

[Feznizzle]

Worked perfect, thanks!

[torvista]

Worked perfect, thanks!

Good to hear, that's the sort of post I'd like to see more often!

[Feznizzle]

I have a zc155e with torvista's version of CEON URI.

Today I noticed that the .htaccess contains a reference to my renamed admin folder:
# Don't rewrite admin directory
RewriteCond %{REQUEST_URI} !^/admin_renamed [NC]

This left me with some questions.

FIRST:
Can the .htaccess be sniffed out? Or is it readable only by my server?

SECOND:
Can I safely remove that "don't rewrite" reference altogether? I experimented with that, deleting it from my .htaccess entirely. There seem to be no problems whatsoever.

THIRD:
I found some code (haven't experimented with it yet) for denying access:

<FilesMatch "^\.ht">
Order allow,deny
Deny from all

Satisfy All
</FilesMatch>

Would applying that code cause any problems?

[Feznizzle]

Never mind, sorry!

Apache is configured by default to deny access to ht files.

[mc12345678]

I have a zc155e with torvista's version of CEON URI.

Today I noticed that the .htaccess contains a reference to my renamed admin folder:
# Don't rewrite admin directory
RewriteCond %{REQUEST_URI} !^/admin_renamed [NC]

This left me with some questions.

FIRST:
Can the .htaccess be sniffed out? Or is it readable only by my server?

SECOND:
Can I safely remove that "don't rewrite" reference altogether? I experimented with that, deleting it from my .htaccess entirely. There seem to be no problems whatsoever.

THIRD:
I found some code (haven't experimented with it yet) for denying access:


Would applying that code cause any problems?

Never mind, sorry!

Apache is configured by default to deny access to ht files.

Glad you figured 1 and 3 out on your own and posted back.
Regarding 2, it somewhat depends on how the directory is called/used. Basically though without an exclusion of the directory, then if that directory is added to the url, it will attempt to be rewritten. If there is no rewrite for that portion of the path then the response will be as if a page is not found, even though the contents may be present.

As the installation test diagnostics indicate, there are various ways that the htaccess can be written to perform the identification of the need to rewrite or to go directly to a folder/file. The specific method implemented prevents access to a new folder that is added to the server by way of the web browser if it is not added to the exclusion list. Another method of implementation is to evaluate the browser path, determine if the path identifies a folder or file, if it does then use that path otherwise send it to be processed by ZC which would perform the rewriting.

[Feznizzle]

Thanks for the additional insight!

[pixelpadre]

We need to update the htaccess file to allow renewal of certificates. The problem is with the .well-known directory and rewrite rules in the htaccess. If I try to renew with the htaccess file I get a server timeout error. If I rename or delete the htaccess file certificate renewal is possible.

[mc12345678]

We need to update the htaccess file to allow renewal of certificates. The problem is with the .well-known directory and rewrite rules in the htaccess. If I try to renew with the htaccess file I get a server timeout error. If I rename or delete the htaccess file certificate renewal is possible.

So what are the contents of your .htaccess file? What is the suggestion for the contents as made by the Ceon URI Mapping installation software as run on your current arrangement?

[pixelpadre]

Geez you really know how to lead a fella around by his nose.............