Nick,
works out the header was actually being added by protocol.c (in
ap_set_content_length)
I've fixed it for what I needed by simply commenting out the body of that
method. This keeps the EAIF MMSC happy and this httpd instance will only be
used for this purpose anyway.
Not sure what the best
On Wed, 25 Jul 2007 10:59:33 +0100
"Daniel JavaDev" <[EMAIL PROTECTED]> wrote:
> Unfortunately it's not my client, but Nokia's EAIF MMSC (emulator in
> this case).
>
> Like I said, I've coded my application to the protocol (EAIF) and it
> works. I only need to add apache httpd in between in order
On 25/07/07, Daniel JavaDev <[EMAIL PROTECTED]> wrote:
Unfortunately it's not my client, but Nokia's EAIF MMSC (emulator in this
case).
Like I said, I've coded my application to the protocol (EAIF) and it works.
I only need to add apache httpd in between in order to restrict access to
the applic
Unfortunately it's not my client, but Nokia's EAIF MMSC (emulator in this
case).
Like I said, I've coded my application to the protocol (EAIF) and it works.
I only need to add apache httpd in between in order to restrict access to
the application (by IP address range).
The response headers witho
On 25/07/07, Daniel JavaDev <[EMAIL PROTECTED]> wrote:
Hi all,
I have the following rules on my apache 2.2.4 config:
RewriteEngine on
RewriteRule ^/someURL http://anotherURL [P]
where someURL is the a publicly available url, and anotherURL is a private
url (localhost on another port). This set
Hi all,
I have the following rules on my apache 2.2.4 config:
RewriteEngine on
RewriteRule ^/someURL http://anotherURL [P]
where someURL is the a publicly available url, and anotherURL is a private
url (localhost on another port). This setup is for restricting access to an
application server.
