Hi Mark,
You can probably override createRequest in your Application class to inject the
header before calling the parent version. Another way could be to add a
property in ERXApplication to "forceWebServerRequests".
public ERXRequest createRequest(String aMethod, String aURL, String
> On 12 Aug 2019, at 14:01, Samuel Pelletier wrote:
>
> Hi Mark,
>
> If you want to simulate a WOAdaotor environment and have the app generate
> static file URL, configure your load balancer to add
> "x-webobjects-adaptor-version" header like I do using apache reverse proxy:
>
>
Hi Mark,
If you want to simulate a WOAdaotor environment and have the app generate
static file URL, configure your load balancer to add
"x-webobjects-adaptor-version" header like I do using apache reverse proxy:
RequestHeader set x-webobjects-adaptor-version "1"
Regards,
Samuel
> Le 12
> On 12 Aug 2019, at 10:03, Matthew Ness via Webobjects-dev
> wrote:
>
>
>
> On Sat, Aug 10, 2019, at 5:54 AM, Mark Gowdy via Webobjects-dev wrote:
>> Hi.
>>
>> Is anyone aware of any security issues (or other considerations) with
>> Direct Connect mode for a live deployment?
>>
>> This
On Sat, Aug 10, 2019, at 5:54 AM, Mark Gowdy via Webobjects-dev wrote:
> Hi.
>
> Is anyone aware of any security issues (or other considerations) with
> Direct Connect mode for a live deployment?
>
> This will be using the Amazon’s Application Load Balancer.
> And it _might_ mean that I can
