I found out what the problem was.
It was related to the fact that when Apache is fronting 4D the remote
IP (browser IP) can't be detected from the request header.
It always returns the address of the machine that Apache is running
on. I imagine it's a catch 22 since this is necessary so that 4D can
return the response back to Apache, however any custom code I have in
Active 4D which uses remote IP's (such as custom firewall, logs and
traffic meter) will now break.
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
