Question
Bug in Apache2 jrun webserver connector
mod_jrun doesn't use the Apache2 API to set the content type.
The correct configuration for mod_deflate however depends on the
content type being set and Apache knowing about the fact:
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/x-javascript
</IfModule>
I found a very helpful blog entry that described the exact solution to this problem, namely this patch to mod_jrun22.c:
# diff mod_jrun22.c.original mod_jrun22.c
756c756,757
< r->content_type = pstrdup_lower(r, value);
---
> // r->content_type = pstrdup_lower(r, value);
> ap_set_content_type(r, pstrdup_lower(r, value));
I used the attached script to recompile the connector; mod_deflate worked fine afterwards.
Does Adobe know about this bug? Do they intend to fix it? As far as I can see, there are quite a lot of other spots, where mod_jrun22.c does not use the Apache-API.
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/x-javascript
</IfModule>
I found a very helpful blog entry that described the exact solution to this problem, namely this patch to mod_jrun22.c:
# diff mod_jrun22.c.original mod_jrun22.c
756c756,757
< r->content_type = pstrdup_lower(r, value);
---
> // r->content_type = pstrdup_lower(r, value);
> ap_set_content_type(r, pstrdup_lower(r, value));
I used the attached script to recompile the connector; mod_deflate worked fine afterwards.
Does Adobe know about this bug? Do they intend to fix it? As far as I can see, there are quite a lot of other spots, where mod_jrun22.c does not use the Apache-API.
AdChoices