Agreed. What i am saying is that, we might need a way to turn this off for
some apps.
On 8 Apr 2015 08:06, "Sumedha Rubasinghe" wrote:
> Yes. But we are talking about apps that are already deployed and have an
> endpoint. So they have gone pass that configuration step.
>
> The problem lies elsewh
Yes. But we are talking about apps that are already deployed and have an
endpoint. So they have gone pass that configuration step.
The problem lies elsewhere. Inside the app, developers can request for
resources like /bookstore/js/stats.js. in other words they assume the root
to be /bookstore.
On
For apps that support context change via config (eg am store) this feature
have to be disabled, right?
On 7 Apr 2015 23:07, "Sumedha Rubasinghe" wrote:
> On Tue, Apr 7, 2015 at 9:35 PM, Sumedha Rubasinghe
> wrote:
>
>> Sajith,
>> Can you make this only applicable to selected web apps only?
>>
>
On Tue, Apr 7, 2015 at 9:35 PM, Sumedha Rubasinghe wrote:
> Sajith,
> Can you make this only applicable to selected web apps only?
>
No need of doing this. :)
The handler will be added to main sequence. That is where all unresolved
requests would go.
>
> On Tue, Apr 7, 2015 at 8:41 PM, Sajith
Sajith,
Can you make this only applicable to selected web apps only?
On Tue, Apr 7, 2015 at 8:41 PM, Sajith Abeywardhana
wrote:
> Hi All,
>
> If webpage containing relative path content there is a problem in gateway
> side in AppM. Please find the full analysis in dev mailing list -
> "[Dev][App
Hi All,
If webpage containing relative path content there is a problem in gateway
side in AppM. Please find the full analysis in dev mailing list -
"[Dev][AppM]App Manager Gateway Test".
Here is the solution for the problem. By using custom mediator we re-write
the all relative path request back t
