I have changed the protocol from "Files/" to "RawData/" and for some reason I can no longer authenticate. Even after a file restart. We are using credentials to pass and login to our server, and this worked fine when we are using "Files/" however, when changing this to "RawData/" this no longer works and is being rejected. 

 

Appreciate any insight/help if anyone has experienced the same.

I want to correct my previous post. The authentication may be working, but the error message states "There is a problem with the SuperContainer base URL: The base URL is configured incorrectly and should point to Files Directory of your super container server." Why would I receive that if I just replaced the "Files/" with "RawData/"?

Hey there,

I am going to assume a few things from your last post:

1. You're using the RawData protocol in the SCSetBaseUrl() Companion plugin function somewhere.

2. You've discovered that you need to use the RawData protocol instead of the usual Files/ for one reason or another in your solution.

Now, to quickly tackle these:

1. There's never a time you will need/should use the RawData/ protocol when setting the base URL. Put simply, replacing the RawData with Files/ in your plugin function call should remedy your error messages.

2. More often than not, the only places you'll have use of the RawData/ protocol are in web viewers... otherwise, it's better and cleaner to just stick to Files/ (I may be forgetting a place or two, but WV is most common).

I hope this helps clear things up.

Signed,