Forcing https?

[Lorelei Adelaide]

HTTPS works for me

[LordHarketh193]

Works for me.

A bit slow though.

[kylie]

     It works for me, tried Explorer and Firefox.

(Firefox seems much faster.  Don't usually use that so not sure if it is a general difference or specific to this.) 

And I'm on wifi in Central Asia at the moment, if that makes any difference to the roster  :-)

[Nessy]

It works for me, but like someone else, now I can't get rid of the new message message.

[RainyHigh]

Https works for me.

[Josietta]

It works for me, but like someone else, now I can't get rid of the new message message.

Try clearing your cookies and cache.   That helped me when I had that issue before.

[Mithlomwen]

Both work for me. 

[AmberStarfire]

Https works fine for me, at least for the most part.

I noticed that some previously-embedded videos from Youtube are now only showing up as hyperlinks, and that's both on the https and http version of the site.

The site also switches back to regular http when I click on your link to come to this thread.

[DarkCassandra]

Both seem to be working fine with me, and HTTPS is equally as fast (though I've used it most of the time anyway) for me.

[stormwyrm]

I actually made a ruleset on HTTPS Everywhere that essentially simulates the effect of the proposed change. So far, I find no oddities anywhere.

[Nessy]

Try clearing your cookies and cache.   That helped me when I had that issue before.

Going back to the the http:// site was easier, and cleared it right up.

[The Infamous]

Wonderful.

[Chris Brady]

I'm all for HTTPS, as long as it's more secure.

As a Canadian National, I'm not comfortable with the potential spying by a foreign agency.  I know it happens and for the most part what we do here isn't very important, but...  I don't know, I just don't like it.  So HTTPS is OK for me.

[Starlequin]

Both are working well for me so far.

[dragonsen]

I actually made a ruleset on HTTPS Everywhere that essentially simulates the effect of the proposed change. So far, I find no oddities anywhere.

Could I get a copy of your ruleset for E until this change is implemented?

[stormwyrm]

For those of you who are interested in trying out the HTTPS Everywhere ruleset. Copy/paste this into Notepad and save it as Elliquiy.xml.

Code Select Expand

<ruleset name="Elliquiy">
  <target host="www.elliquiy.com" />
  <target host="elliquiy.com" />

  <rule from="^http://(www\.)?elliquiy\.com/" to="https://elliquiy.com/"/>
</ruleset>


Then, in Firefox, go to Help->Troubleshooting Information and under the Application Basics section, click on Open Containing Folder. There a window will appear and you should copy the Elliquiy.xml file inside the HTTPSEverywhereUserRules folder. Then restart your browser. These instructions of course are specific for Windows. Not sure how it's done on OS X or any other OS but it boils down to putting the ruleset in the folder where user rules are stored, and restarting the browser (or alternatively disabling and re-enabling HTTPS Everywhere).

[TheRedWind]

Works for me.

[Marikir]

Good on my end, I believe.

[Rook Seidhr]

I've had an HTTPSEverywhere rule forcing https access site-wide ever since I joined E, and it works fine except for uploading files to the wiki. I have to turn it off and use http to get that to work.

[Athem]

Same here, except I use the option in NoScript (for Firefox) to force https.

[Naomi75]

I suppose whatever works for you works for me! LOL Thanks for asking but I'm tech challenged so I defer to your judgment!

[Cthonig]

Both work for me.

[realisticwordweaver]

Search does not work for me either ways

[Indyo]

Works fine here, Veks :)

[Vekseid]

For those of you who are interested in trying out the HTTPS Everywhere ruleset. Copy/paste this into Notepad and save it as Elliquiy.xml.

Code Select Expand

<ruleset name="Elliquiy">
  <target host="www.elliquiy.com" />
  <target host="elliquiy.com" />

  <rule from="^http://(www\.)?elliquiy\.com/" to="https://elliquiy.com/"/>
</ruleset>


Then, in Firefox, go to Help->Troubleshooting Information and under the Application Basics section, click on Open Containing Folder. There a window will appear and you should copy the Elliquiy.xml file inside the HTTPSEverywhereUserRules folder. Then restart your browser. These instructions of course are specific for Windows. Not sure how it's done on OS X or any other OS but it boils down to putting the ruleset in the folder where user rules are stored, and restarting the browser (or alternatively disabling and re-enabling HTTPS Everywhere).

Could you add securecookie to that and check to make sure it works, please?

Code Select Expand

<ruleset name="Elliquiy">
  <target host="www.elliquiy.com" />
  <target host="elliquiy.com" />

  <rule from="^http://(www\.)?elliquiy\.com/" to="https://elliquiy.com/"/>
  <securecookie host="^(\.)?elliquiy\.com$" name="(ElliSMFCookie11|PHPSESSID)" />
</ruleset>