On Wed, Oct 9, 2024 at 5:31 AM Abhijith wrote:
> Thanks I understand. But can you suggest any debugging method to find out
> which file is requesting the file
>
> On Wed, 9 Oct 2024, 10:37 Frank Gingras, wrote:
>
>>
>>
>> On Tue, Oct 8, 2024 at 11:25 PM Abhijith wrote:
>>
>>> Yes, I understand
Thanks I understand. But can you suggest any debugging method to find out
which file is requesting the file
On Wed, 9 Oct 2024, 10:37 Frank Gingras, wrote:
>
>
> On Tue, Oct 8, 2024 at 11:25 PM Abhijith wrote:
>
>> Yes, I understand that now. That I shouldn't allow clients to access my
>> .htt
On Tue, Oct 8, 2024 at 11:25 PM Abhijith wrote:
> Yes, I understand that now. That I shouldn't allow clients to access my
> .httaccess file. I don't know why the error occuring
>
> On Tue, 8 Oct 2024, 17:47 Frank Gingras, wrote:
>
>>
>>
>> On Tue., Oct. 8, 2024, 1:13 a.m. Abhijith,
>> wrote:
>
Yes, I understand that now. That I shouldn't allow clients to access my
.httaccess file. I don't know why the error occuring
On Tue, 8 Oct 2024, 17:47 Frank Gingras, wrote:
>
>
> On Tue., Oct. 8, 2024, 1:13 a.m. Abhijith, wrote:
>
>> Hi,
>> Yes, In the the root directory there is .htaccess fil
On Tue., Oct. 8, 2024, 1:13 a.m. Abhijith, wrote:
> Hi,
> Yes, In the the root directory there is .htaccess file, the content of the
> file is
> ```
> RewriteEngine on
> RewriteCond %{REQUEST_FILENAME} !-f
> RewriteCond %{REQUEST_FILENAME} !-d
> RewriteCond $1 !^(index\.php|robots\.txt|favicon\.i
Hi,
Yes, In the the root directory there is .htaccess file, the content of the
file is
```
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond $1 !^(index\.php|robots\.txt|favicon\.ico)
RewriteRule ^(.*)$ /index.php/$1 [L]
```
Since by @Eric's sugge
On Mon, Oct 7, 2024 at 7:51 AM Eric Covener wrote:
> On Mon, Oct 7, 2024 at 7:12 AM Eric Covener wrote:
> >
> > >> [Sun Oct 06 10:02:48.889047 2024] [authz_core:error] [pid 10:tid
> 131326541519672] [client 192.168.16.1:49194] AH01630: client denied by
> server configuration:
> /usr/local/apache
On Mon, Oct 7, 2024 at 7:12 AM Eric Covener wrote:
>
> >> [Sun Oct 06 10:02:48.889047 2024] [authz_core:error] [pid 10:tid
> >> 131326541519672] [client 192.168.16.1:49194] AH01630: client denied by
> >> server configuration:
> >> /usr/local/apache2/htdocs/apps/admin/public_html/.htaccess
>
> T
Thanks for the response,
There is no other config file than admin.conf.
here is the result of `apachectl -S`:
```
[Mon Oct 07 11:30:45.926201 2024] [core:trace3] [pid 102:tid
123653751024456] core.c(3469): Setting LogLevel for all modules to trace8
[Mon Oct 07 11:30:45.926287 2024] [core:trace3] [p
>> [Sun Oct 06 10:02:48.889047 2024] [authz_core:error] [pid 10:tid
>> 131326541519672] [client 192.168.16.1:49194] AH01630: client denied by
>> server configuration:
>> /usr/local/apache2/htdocs/apps/admin/public_html/.htaccess
This error means it's not filesystem permissions. Are there other
Hi all,
I’m working on Dockerizing a PHP application and configuring Apache, but
I’m encountering an issue related to `.htaccess` that I can’t seem to
resolve. I’d greatly appreciate any guidance from the community!
Here’s the setup I’m working with:
*Docker Compose File (docker-compose.yml):*
to elaborate more, the first page comes up fine, and which is exactly same
for app1 and app2 (these are exactly the same apps just separated by
instances to have different configurations in the UI, and assigned for
different groups doing the same functionality), problem comes up when i hit
on any o
Thanks Tobias, the second option is not feasible, and this all has to be
part of the same domain.
On Tue, Dec 29, 2015 at 7:24 PM, Tobias Adolph wrote:
> HI Chetan,
>
> you could place them in different virtual-Host-Container (which means
> different domains) or you could alter the url-part
> (/
niether of it works, for some unknows reason it tried to look for /app1
under document root.
On Tue, Dec 29, 2015 at 7:54 PM, Yann Ylavic wrote:
> On Tue, Dec 29, 2015 at 3:16 PM, Yann Ylavic wrote:
> >
> > You possibly need something like:
> >
> > RewriteRule ^/app1/(.*)
> > http://host_
On Tue, Dec 29, 2015 at 3:16 PM, Yann Ylavic wrote:
>
> You possibly need something like:
>
> RewriteRule ^/app1/(.*)
> http://host_name1:app1_port/app/WebObjects/app.woa/$1 [P]
> RewriteRule ^/app2/(.*)
> http://host_name2:app2_port/app/WebObjects/app.woa/$1 [P]
> http://host_name1:ap
Hi,
On Fri, Dec 18, 2015 at 2:35 PM, chetan jain wrote:
>
> #For app-1
>
>RewriteRule ^/app1$ /app1/ [R]
>RewriteRule ^/app1/(.*) /app/WebObjects/app.woa/$1 [P]
>ProxyPass /app/WebObjects/app.woa/
> http://host_name1:app1_port/app/WebObjects/app.woa/
>ProxyPassReverse /app/WebObj
HI Chetan,
you could place them in different virtual-Host-Container (which means
different domains) or you could alter the url-part
(/app/WebObjects/app.woa) to another string (like
/app/webObjects/app1|2.woa) that is different for each backend.
Regards,
Tobias
Am 29.12.2015 um 14:43 schrie
Thanks Tobias,
The problem with that would be, I won't be able to ProxyPass with path in
Location bock.
--Chetan
On Tue, Dec 29, 2015 at 4:03 PM, Tobias Adolph wrote:
> Hi Jain,
>
> did you configure those in the same virtualhost-Block?
>
> Am 18.12.2015 um 14:35 schrieb chetan jain:
>
> #For
Hi Jain,
did you configure those in the same virtualhost-Block?
Am 18.12.2015 um 14:35 schrieb chetan jain:
#For app-1
RewriteRule ^/app1$ /app1/ [R]
RewriteRule ^/app1/(.*) /app/WebObjects/app.woa/$1 [P]
ProxyPass /app/WebObjects/app.woa/
http://host_name1:app1_port/app/WebObjects/a
Hi all,
I have a scenario where i have different instances of the same application
deployed on different boxes and we call those instances as app1, app2.
and the actual URL for both will be like this :
http://host_name1:app1_port>/app/WebObject/app.woa for app1
http://host_name2:app2_port/
20 matches
Mail list logo