Discussion:
adding www, to link or url prefix
(too old to reply)
lisa
2024-05-29 08:18:37 UTC
Permalink
if I click on a website link in Agent like : xyz.com Agent translated
that in www.xyz.com
That gives certificate errors because the certificate is only valid
for xyz.com and not for www.xyz,com
I searched in Agent.ini for www and found this entry :

Pattern6=<((url:|URL:)
*)?(([a-zA-Z][a-zA-Z0-9.+\-]+:|www\.|WWW\.|ftp\.|FTP\.|icq#|ICQ#)[^>]*)>|(^|[>|:<
\t\(\[{"])(url:|URL:)?(([a-zA-Z][a-zA-Z0-9.+\-]+:|www\.|WWW\.|ftp\.|FTP\.|icq#|ICQ#)[^
\t<>"{}|\^`()[\]]+|[^,:;@<> \t()[\]"]+@[^,:;@<> \t()[\]"]*)

I have no idea if this is related to my problem and how or if I have
to change it or just strip the www. part in my browser to avoid
certificate problems.
Arthur T.
2024-05-29 19:09:14 UTC
Permalink
Post by lisa
if I click on a website link in Agent like : xyz.com Agent translated
that in www.xyz.com
That gives certificate errors because the certificate is only valid
for xyz.com and not for www.xyz,com
Pattern6=<((url:|URL:)
*)?(([a-zA-Z][a-zA-Z0-9.+\-]+:|www\.|WWW\.|ftp\.|FTP\.|icq#|ICQ#)[^>]*)>|(^|[>|:<
\t\(\[{"])(url:|URL:)?(([a-zA-Z][a-zA-Z0-9.+\-]+:|www\.|WWW\.|ftp\.|FTP\.|icq#|ICQ#)[^
This is probably not related to your problem. From Agent's help:
This setting specifies the regular expression used to match URLs. The
expression consists of a union of subexpressions, each of which
matches a particular URL format. Each subexpression consists of a
prefix pattern, followed by a parenthesized expression that matches
the actual URL text.

So my take on that is that it helps Agent recognize URLs, but doesn't
change them. And, in fact, my Agent (1.93) recognizes www.xyz.com as
a link, but doesn't recognize xyz.com as one.

I'd look at the message in raw mode and see if the link has www, but
it isn't being displayed. You might also try copy/pasting the link
into the browser and see if the browser is adding the www.
--
Arthur T. - ar23hur "at" pobox "dot" com
Paul S Person
2024-05-30 15:23:29 UTC
Permalink
Post by Arthur T.
Post by lisa
if I click on a website link in Agent like : xyz.com Agent translated
that in www.xyz.com
That gives certificate errors because the certificate is only valid
for xyz.com and not for www.xyz,com
Pattern6=<((url:|URL:)
*)?(([a-zA-Z][a-zA-Z0-9.+\-]+:|www\.|WWW\.|ftp\.|FTP\.|icq#|ICQ#)[^>]*)>|(^|[>|:<
\t\(\[{"])(url:|URL:)?(([a-zA-Z][a-zA-Z0-9.+\-]+:|www\.|WWW\.|ftp\.|FTP\.|icq#|ICQ#)[^
This setting specifies the regular expression used to match URLs. The
expression consists of a union of subexpressions, each of which
matches a particular URL format. Each subexpression consists of a
prefix pattern, followed by a parenthesized expression that matches
the actual URL text.
So my take on that is that it helps Agent recognize URLs, but doesn't
change them. And, in fact, my Agent (1.93) recognizes www.xyz.com as
a link, but doesn't recognize xyz.com as one.
Nor does mine (Agent 8.0).

But, when I highlight it and pull up the context menu (menu key or
right-click [for a right-handed trackball]) and select "Launch URL",
Edge brings up https://gen.xyz/ (which will allow you to create and
register a domain name ending in ".xyz").

Note: when highlighting, it helps to /not/ include the space before
the "x", as, if it is included, Edge reports it can't reach the page
"%20xyz.com/".

Agent never ceases to do amazing things.
Post by Arthur T.
I'd look at the message in raw mode and see if the link has www, but
it isn't being displayed. You might also try copy/pasting the link
into the browser and see if the browser is adding the www.
--
"Here lies the Tuscan poet Aretino,
Who evil spoke of everyone but God,
Giving as his excuse, 'I never knew him.'"
Ralph Fox
2024-05-29 20:06:12 UTC
Permalink
Post by lisa
if I click on a website link in Agent like : xyz.com Agent translated
that in www.xyz.com
That gives certificate errors because the certificate is only valid
for xyz.com and not for www.xyz,com
Pattern6=<((url:|URL:)
*)?(([a-zA-Z][a-zA-Z0-9.+\-]+:|www\.|WWW\.|ftp\.|FTP\.|icq#|ICQ#)[^>]*)>|(^|[>|:<
\t\(\[{"])(url:|URL:)?(([a-zA-Z][a-zA-Z0-9.+\-]+:|www\.|WWW\.|ftp\.|FTP\.|icq#|ICQ#)[^
I have no idea if this is related to my problem and how or if I have
to change it or just strip the www. part in my browser to avoid
certificate problems.
As Arthur T has replied, that setting is not related to your problem.

Agent does not add "www." to links when launching them.
Here are three ways in which the "www." could be added:

1. You are looking at an HTML message. The text says xyz.com.
But when you hover over the xyz.com the HTML link which shows
in Agent's status bar is www.xyz.com.
In HTML messages this actual link is set by the sender, not by Agent.

In plain text messages, xyz.com is _not_ a clickable link.
To be clickable, it would have to be http://xyz.com or https://xyz.com.
So I am guessing this is an HTML message, where the sender sets
the actual link.


2. If the site xyz.com is not found, many or most web browsers will
add a "www." and try again.

As a test, try these two commands from a Command Prompt (cmd.exe)
window.

nslookup -type=A xyz.com

nslookup -type=A www.xyz.com


3. When you go to xyz.com, some websites will automatically redirect
the web browser to www.xyz.com. This redirection can happen so
fast that you never see just xyz.com in the browser's URL bar.

If a web site is redirecting you from xyz.com to www.xyz.com but
the certificate is for xyz.com and not www.xyz.com then the site
is badly configured. But such mistakes do happen.
--
Kind regards
Ralph Fox
🦊

Look before you leap, For snakes among sweet flowers do creep.
lisa
2024-05-30 09:58:23 UTC
Permalink
Post by Ralph Fox
Post by lisa
if I click on a website link in Agent like : xyz.com Agent translated
that in www.xyz.com
after reading your replies, indeed, Agent doesn't translated it or
manipulated it.
Post by Ralph Fox
1. You are looking at an HTML message. The text says xyz.com.
But when you hover over the xyz.com the HTML link which shows
in Agent's status bar is www.xyz.com.
In HTML messages this actual link is set by the sender, not by Agent.
that's the case
Post by Ralph Fox
In plain text messages, xyz.com is _not_ a clickable link.
To be clickable, it would have to be http://xyz.com or https://xyz.com.
So I am guessing this is an HTML message, where the sender sets
the actual link.
If a web site is redirecting you from xyz.com to www.xyz.com but
the certificate is for xyz.com and not www.xyz.com then the site
is badly configured. But such mistakes do happen.
the link is redirecting me from xyz.com to www.xyz.com

yeah, when I look at the reply xyz.com it's indeed not a clickable
link. It doesn't look like as a HTML message for me, but it must be
the case. I thought I had unchecked the box "Allow HTML content to
be displayed" in the past but it wasn't turned off.
Turning it off and most messages are no longer readable. Turning it
off is not a good idea if I want to read the content of a message.
And yes, that message was complete HTML

Thanks for solving this "problem" for me.
Ralph Fox
2024-05-31 00:34:28 UTC
Permalink
Post by lisa
Thanks for solving this "problem" for me.
You're welcome.

Loading...