not sure if this a problem of the https: switch, or if it was there before.
But i have a little problem with writing and previewing posts AND PM's.
You can test it easily. Write up some large text for a post or PM and press Preview (first time always works) then change little bits and do the Preview again.
I get two cases: Either a text will pop up telling me "Direct access is not allowed!!!" or i get nothing, no preview window, no text, no telling me not what's going on.
One more thing when writing PM's. Once i sent it (after i got the "Direct access is not allowed!!!" bit i get a completely blank browser window with only the link "or close this window") I remember having some more information displayed, something like "PM succesfully sent, you can do this or that or "close this window". Something like that. Don't want to annoy anyone with test PM's.
@templario If your OWB version at your SAM is 1.26, I guess it is a really old version. You should try a newer one. Also, in the documentation of OWB there is a proposed ENV variable that disables SSL check, which the developer proposes to set in case there are issues with SSL.
I'm not sure if it's https related but I'm finding that since aproximatly the time https testing was announced OWB 3.30 runs at 100% CPU after loading about 65Kb of data. It never seems to recover, only happens on amigans.net as far as I can tell, though other sites do render slowly! Due to OWB having limited features it's hard to see exactly which file connection is causeing the slow down.
Works fine in Odyssey though. I do prefer OWB on my SAM as the fonet rendering is smoother, though it's gradually getting harder to use anyway on the wider net often due to asynchronous css styles that cause multiple rerendering of the page, (whichever google engineer though that was a good idea needs taking out and reeducating! but I digress....) this doesn't appear to be that problem though as no page is rendered at all.