From: "Jesse Tayler" <webobjects-dev@wocommunity.org>
Received-SPF: none
 receiver=post.selbstdenker.com; client-ip=209.85.219.44; envelope-from=jtayler@oeinc.com
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Subject: Re: [WO-DEV] Stupid me but how do I generate a fully qualified direct
 action url for sending out via mail?
Date: Tue, 16 Feb 2021 18:16:11 -0500
References: <list-25418812@post.selbstdenker.com>
To: WebObjects & WOnder Development <webobjects-dev@wocommunity.org>
In-Reply-To: <list-25418812@post.selbstdenker.com>
Message-Id: <DAFF6FEB-CD3F-4096-B299-88428004C542@oeinc.com>

I went to see what I was doing maybe this helps.=20

ERX class here handles deployment URLs properly so I don=E2=80=99t need =
to fuss there if I generate my URL from here

ERXRouteUrlUtils.actionUrlForEntity

I have a simple function

	public static String cleanedLink(String link) {

That actually uses D2W to contain a dictionary of replacements, to =
shorten specific URLs that likely match to an apache rule that unpacks =
it to the full endpoint URL in WO and I might use it for simple static =
page DA urls

  "truanon/wa/about" =3D "about=E2=80=9D;=20

That=E2=80=99s how I seem to do very short links in production, while =
not having issue while in development and seems to work fine.

I get the domain from an ERX class

		String applicationHost =3D =
ERXConfigurationManager.defaultManager().hostName();

Because I run staging and developer machines etc.

"http://" + applicationHost + "/verify?

Produces a shortened URL I can send in email that is expected to run on =
whichever host sent it.


> On Feb 16, 2021, at 5:44 PM, Paul Hoadley =
<webobjects-dev@wocommunity.org> wrote:
>=20
> On 17 Feb 2021, at 01:21, Susanne Schneider =
<webobjects-dev@wocommunity.org> wrote:
>=20
>> this is indeed not so trivial as you could think, at least I did not =
find an easy way. You can ask the application to get the name of itself, =
ask the WOAdaptor for the adaptor part, but you cannot find out the name =
of the server, especially if your installation is behind a firewall or =
proxy and the external server name is different from the internal name.
>>=20
>> We finally used a custom configuration parameter to get the server =
name (including the adaptor path) and startet from there on, something =
like:
>> url =3D servername + applicationname + ".woa/wa/" + yourActionName
>=20
> And then if you're using re-writing to shorten the URL, it gets even =
more complicated to do it in a general way. We pretty much gave up =
completely, and most apps now have a property like this:
>=20
> net.logicsquad.example.directActionUrl=3Dhttps://example.com/app/wa
>=20
>=20
> --=20
> Paul Hoadley
> https://logicsquad.net/
> https://www.linkedin.com/company/logic-squad/
>=20
>=20
>=20