On 13 Oct 2009, at 02:16, Jyri Virkki wrote:
> Nick Kew wrote:
>>
>> I've updated it with your suggestions.
>>
>> I've made one other change: the ARC case referenced
>> for Apache 2.2 was a minor update, so I switched to
>> the ARC case to include the first Apache 2.2 package
>> in OpenSolaris. H
Nick Kew wrote:
>
> I've updated it with your suggestions.
>
> I've made one other change: the ARC case referenced
> for Apache 2.2 was a minor update, so I switched to
> the ARC case to include the first Apache 2.2 package
> in OpenSolaris. Hope that makes sense.
Looks good. I did some minor co
Nick Kew wrote:
>
> >> 3.2 Market/Requester
> >>mod_proxy_html has been requested by Web Stack users and
> >>by the originator.
> >
> >What does "and by the originator" means above?
>
> I proposed these and other modules myself last year!
Ah.. the question is more about what are the busin
Jyri Virkki wrote:
> [chop]
I've updated it with your suggestions.
I've made one other change: the ARC case referenced
for Apache 2.2 was a minor update, so I switched to
the ARC case to include the first Apache 2.2 package
in OpenSolaris. Hope that makes sense.
--
Nick Kew
-- ne
On 9 Oct 2009, at 04:39, Jyri Virkki wrote:
> Nick Kew wrote:
>>
>> 3.2 Market/Requester
>> mod_proxy_html has been requested by Web Stack users and
>> by the originator.
>
> What does "and by the originator" means above?
I proposed these and other modules myself last year!
>> 4.1 De
Nick Kew wrote:
>
> 3.2 Market/Requester
> mod_proxy_html has been requested by Web Stack users and
> by the originator.
What does "and by the originator" means above?
> 4.1 Details
> This is a straightforward packaging effort. The main technical issue
> to deal with
Nick Kew wrote:
> We'd like to include these Apache modules in future releases.
> They serve to enable the Apache proxy to act as a gateway to
> web-based systems, even where such systems generate HTML
> links that are not accessible (or even addressable) from
> the outside world, and so would not
We'd like to include these Apache modules in future releases.
They serve to enable the Apache proxy to act as a gateway to
web-based systems, even where such systems generate HTML
links that are not accessible (or even addressable) from
the outside world, and so would not work through a "normal"
HT
