Initial test – three questions

During initial testing of SEB 3.0, I noticed three things. I don’t know if these are known issues:

1) Using Microsoft Edge, sebs:// links don’t trigger a start of SEB (nothing happens). Using Chrome, SEB is launched. 2) Using a sebs://-link from Chrome starts SEB but triggers a “Configuration Error” message saying the resource is not supported, and SEB is quit. If I download the exact contents of the same URL and save it as an .seb-file, it all works as expected, so there’s nothing wrong with the actual configuration.

Let me know if these are not known issues and if you want me to post a link that behaves in this way for me.

1. Cookies seem to be cleared between launches, as chosen language is not remembered.

[Krisell]

Regarding your other point, I don’t think there is any caching in the .NET API I am using, I however did not investigate this in great detail. There is a ton of work involved in writing a feature-rich application like SEB single-handed, I simply don’t have the capacity to test out every minute detail. If you’d like to know it exactly, feel free to debug / test it yourself. I certainly aspire to improve the code whenever and wherever I can…

I’ll take a look at the caching when I get the chance. It should be easy to test considering that there are two identical requests now if I reject the initial HEAD.

If there aren’t any other issues, I suggest we close this one for now?

Absolutely, closed.

[dbuechel]

Great, thanks for investigating!