Ok, I tried the following one with no luck. The requests are always going
to the new host without the customer header value also.
cond %{HEADER:DEV_HOST} = "dev102"
set-destination HOST dev102.abc.com [L]
my remap rule is
map / http://abc.com/ @pristine_host_hdr=1 @plugin=header_rewrite.so
@pparam=my_header_rules.conf
Am I missing anything important here?
Thanks
Adi
On Tue, Jan 24, 2017 at 11:46 AM, Jeremy Payne <[email protected]> wrote:
> the lua plugin also has this functionality although may be somewhat
> overkill for your needs.
>
>
> On Tue, Jan 24, 2017 at 1:43 PM, Adi Mallikarjuna Reddy V <
> [email protected]> wrote:
>
>> So to achieve my use case, can I try something like this?
>>
>> map / http://b.bar.com @plugin=header_rewrite.so @pparam=rules1.conf
>>
>> and my rules1.conf has
>>
>> cond %{HEADER:MY_HEADER} = "foo"
>> set-destination HOST mobile.bar.com [L]
>>
>> This should forward the request to mobile.bar.com if the request has
>> 'MY_HEADER' with value 'foo'.
>>
>>
>> Thanks
>>
>> Adi
>>
>>
>>
>> On Tue, Jan 24, 2017 at 11:36 AM, Brian Geffon <[email protected]>
>> wrote:
>>
>>> Sorry I think I meant header_rewrite.
>>>
>>> Brian
>>>
>>> On Tue, Jan 24, 2017, 11:26 Brian Geffon <[email protected]> wrote:
>>>
>>>> There is a regex_remap plugin that is what you would want, take a look
>>>> in plugins/
>>>>
>>>> Brian
>>>>
>>>>
>>>> On Tue, Jan 24, 2017, 11:25 Adi Mallikarjuna Reddy V <
>>>> [email protected]> wrote:
>>>>
>>>> Is there a config that allows to change remap rule based on the
>>>> incoming header?
>>>>
>>>>
>>>> My use case is , if I send a custom header in the request, the remap
>>>> rule should be changed to different one than the default one configured.
>>>>
>>>>
>>>> Thanks
>>>>
>>>> Adi
>>>>
>>>>
>>
>
