On Mac OS X Server httpd.conf contains the config
DefaultType text/plain
which tells apache how to respond if it can't determine the content
type.
If I change this to DefaultType text/html and restart Apache the
problem goes away, but I am wondering what unintended side-affects
that might have?
What is odd is that Apache 1 is configured w/ DefaultType text/plain
and the problem doesn't appear.
Has something have changed between Active 4.0 and 5.0 where the
default error pages would not have had a content type? Could
something in my Active4D 5 configuration cause that?
I installed httpfox into Firefox on the server machine .
I made a request for a non-existent a4d file at
http://localhost:8080/admin/nofile.a4d
Active4D returned it's internal 404. The response headers were
(status line) HTTP/1.1 404 Not Found
Connection Close
That's it. No content-type.
I then made a request for the same non-existent file on our
production server which is still running Apache 1, 4D 2003, and
Active4D 4.
Active4D returned it's internal 404. The expected response headers
including a Content-Type text/html exist.
That is the cause of the problem. Question is how to solve it?
-- Brad
On 11/19/10 3:22 PM, Brad Perkins wrote:
> I'm just now getting back to this and have discovered something but
> am stumped about the solution.
>
> This is running Active4D 5.0 (latest)
> 4D Remote (client) v11.8
> NTK Web Server configured to only accept requests from local hosts.
> Apache 2 is in front of 4D.
>
> The problem was/is that some Active4D error pages are serving as
> type text/plain. The html text response displays in the browser.
> Through trial and error I discovered that if make a localhost:8080
> call on the web server machine to a page that would give that error,
> the expected Active4D error response serves fine.
> That request is bypasssing Apache. So this isn't an Active4D
> problem. It is either an Apache config issue or something with my
> rewrite rules. Our old system was running Apache 1. My rewrite rules
> haven't changed.
>
> Would anyone have any idea where to look in Apache configs to find
> what might be causing an Active4D error response to be passed
> through and served by Apache as text/plain?
>
> Thanks,
>
> Brad
>
> On 9/21/10 3:31 PM, Brad Perkins wrote:
>> On 9/21/10 9:51 AM, Aparajita Fishman wrote:
>>>> That setting is left blank
>>> Then I'm stumped, I can't reproduce it.
>>>
>> Can I expect creating a custom error page to solve this?
>>
>> I only ask because I've always used the default, have other
>> priorities, and don't want to figure out how to create a custom page
>> if it isn't likely to solve the problem.
>>
>> Thanks,
>>
>> Brad
>> _______________________________________________
>> Active4D-dev mailing list
>> [email protected]
>> http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
>> Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
>>
> _______________________________________________
> Active4D-dev mailing list
> [email protected]
> http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
> Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
>
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
