OS4 final and AmiSSL

Can somebody explain me why (using AWeb) each time I come to this website (that's not the only one, but this is the one I come more often I have a requester to insert 'AmiSSL:' in any drive ?
That's strange because all I have to do is to click on the "Assign" button, then in the ASL requester, I right click to view volumes and assigns list and I always select my assign called AmiSSL
That wasn't the case before adding the paypal donation button and wasn't the case with previous updates either...

@abalaban

Seems to be a "wrong" AmiSSL assign (or a doubled somewhere).

Check your user-startup fpr pre final AmiSSL: assigns and
remove them, no need since final

@Raziel

This is here the best part : those AmiSSL that already exists is not created by me, it comes from the startup-sequence (see line 22). What I don't understand is why if there is already an assign it keeps on demanding it ? Also I have noted it's only once by session (i.e. time between reboots).

@abalaban

Line 22 in Startup-Sequence is AmigaOS4's AmiSSL install,
since final "official" part of AmigaOS.

1. Do a reboot and then type assign in a shell window, there
you'll see where your AmiSSL assign goes, i suspect an
external program is interfering (maybe some program adds an
assign on startup without using ADD and deleting the OS4
AmiSSL one)?

2. If the behaviour is reproduceable, let Snoopy
run before it happens and see what happens exactly.

@Raziel

I don't see anything interfering with AmiSSL assign...
Let's see the following snapshot :


Snoopy does not say much, except that an AWeb Retreive task is trying to access AmiSSL:certs

@abalaban

Have you noticed that Startup-Sequence sets up AMISSL: and AWeb looks for AmiSSL: ?

@ZeroG

Yep I have noticed that and tried to change the case in the startup sequence, that's why you can see an AmiSSL assign in my shell output above. As you can see that does not change anything...

And are you telling me that Amiga volume name is becoming case sensitive ?

Huh???

What have become of my answer post?

Dang, next try

@abalaban

It never was case sensitive (OS-level - well, maybe it was
with preOS3 versions, but it shouln't make any difference
nowadays).

There's either something wrong with your SSL install or the
DEFER mode doesn't kick in (for reasons i don't know).

Try the following:

Comment out DEFER and let the assign be there from the start

C:Assign AMISSL: DEVS:AMISSL ;DEFER

and see what happens

@Raziel

Ok I can't reproduce it anymore, does anyone changed something on the site ? Or was it the DEFER option to assign that did not work ?

@abalaban

Again removing the DEFER argument just cured the problem or else someone did changed something on this site ??
Thank you Raziel for the idea