thx - yes we should do this but yet all sites like wiki etc are hosted on different vps ... will add conflicted files local now!

Thanks for your help arhag

Quote from: cass on February 03, 2015, 08:33:25 AM
ok https is gonna cause issues with the tickers, since svk doesn't has an https api server yet!

That isn't all:

Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure resource 'http://code.highcharts.com/stock/highstock.js'. This request has been blocked; the content must be served over HTTPS.
bitshares.org/:1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure resource 'http://code.highcharts.com/stock/modules/exporting.js'. This request has been blocked; the content must be served over HTTPS.
bitshares.org/:1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Roboto:700,400,300,200,100'. This request has been blocked; the content must be served over HTTPS.
(index):152 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://faucet.bitshares.org/widgets/1/w.js?ref='. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://code.highcharts.com/stock/highstock.js'. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://code.highcharts.com/stock/modules/exporting.js'. This request has been blocked; the content must be served over HTTPS.
jquery.js:8693 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://api.bitsharesblocks.com/v1/cmc?callback=jQuery21305609141846653074_1422953063792&format=json&_=1422953063793'. This request has been blocked; the content must be served over HTTPS.
jquery.js:8625 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://coinmarketcap-nexuist.rhcloud.com/api/bts?format=json'. This request has been blocked; the content must be served over HTTPS.
app.js:80 Object {readyState: 4, getResponseHeader: function, getAllResponseHeaders: function, setRequestHeader: function, overrideMimeType: function...}
jquery.js:8693 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://api.bitsharesblocks.com/v3/pricehistory/USD/%7B%22start%22:%222015-0...0Z%22%7D?callback=jQuery21305609141846653074_1422953063792&_=1422953063794'. This request has been blocked; the content must be served over HTTPS.


First, you can use HTTPS with code.highcharts.com and fonts.googleapis.com and coinmarketcap-nexuist.rhcloud.com. Then that just leaves faucet.bitshares.org and api.bitsharesblocks.com.

Also, why are we not hosting the various javascript scripts that we are using ourselves rather than linking to other sites (even if it's over HTTPS) to provide them, such as highcharts, jquery, google, facebook, to name a few (not to mention others from hosts I know nothing about and don't personally trust).

And, rather than using JSONP to get data from api.bitsharesblocks.com, I would prefer if svk could enable CORS on api.bitsharesblocks.com for at least the bitshares.org origin (but he might as well do it for * so that anyone can use that data without JSONP).

pls use github for issues

https://github.com/cassiopaia/labs.bitshares.org

or

https://github.com/BitShares/bitshares.org

ok https is gonna cause issues with the tickers, since svk doesn't has an https api server yet!

Quote from: arhag on February 03, 2015, 06:14:03 AM
But please make the website redirect to HTTPS if it is accessed through HTTP.

I think you need this in .htaccess:

Code Select Expand


RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://bitshares.org/$1 [R,L]


done

Quote
Also, something has got to be done about subdomains like wiki.bitshares.org and faucet.bitshares.org. Those cannot be accessed through HTTPS. So you would want to make those available on the bitshares.org domain instead and set up .htaccess to redirect to https://bitshares.org/wiki/$1 and https://bitshares.org/faucet/$1 for example. Also, before changing the faucet domain, we better be sure it doesn't break account registration from the BitShares client.

yeah - we've  ordered a wildcard ssl cert .. so guess this should ne problem .. will check it later on .. guess i've to send ssl .crt .key .. etc to wiki and faucet vps server admin, so they can include it ony their server structure!? Or i'm wrong with this!?

Quote from: cass on February 03, 2015, 04:58:36 AM
SSL is working now! Thx to stan

https://bitshares.org/resources/downloads

+5%

But please make the website redirect to HTTPS if it is accessed through HTTP.

I think you need this in .htaccess:

RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://bitshares.org/$1 [R,L]


Also, something has got to be done about subdomains like wiki.bitshares.org and faucet.bitshares.org. Those cannot be accessed through HTTPS. So you would want to make those available on the bitshares.org domain instead and set up .htaccess to redirect to https://bitshares.org/wiki/$1 and https://bitshares.org/faucet/$1 for example. Also, before changing the faucet domain, we better be sure it doesn't break account registration from the BitShares client.

SSL is working now! Thx to stan

https://bitshares.org/resources/downloads

Quote from: cass on February 02, 2015, 09:10:08 PM
@stan, dan : any reply to my ssl cert approval request  (it was send to admin[at]bitshares.org) !? We have to install SSL asap IMO!

Feeback appreciated!

+5%

@stan, dan : any reply to my ssl cert approval request  (it was send to admin[at]bitshares.org) !? We have to install SSL asap IMO!

Feeback appreciated!

 +5% love those individual colors for each of the bitassets!

Quote from: xiahui135 on February 02, 2015, 02:54:44 PM
i must say it is very simple!

? you mean site? .. yes it should be ... doesn't it?

QuoteAfter this how about provide different language ?

language support will be added soon ...

i must say it is very simple!
After this how about provide different language ?

QuoteIEs (9 to be specific - of course a pain for sure and really not a biggie in regard of importance but should be taken care of later).

yes maybe i'll check this later on .. but honestly ... it's a mess to get sites generelly working in older browers ...

Quote from: mudshark79 on February 01, 2015, 09:25:11 PM
While you are at it looking for the cert and stuff please also double check overall speed of the site, got some mixed results really, opening and trying the download link (checked from 4 different locations whereas it appeared reaaly slow from at least two). Maybe you can beef up server-provider side?

More serious: there are at least 5 HTTP500 timeouts for some font-files referenced + at least one javascript error. Also cross-browser testing shows the site isn't working in older IEs (9 to be specific - of course a pain for sure and really not a biggie in regard of importance but should be taken care of later).

So just a little nit-picking from my end  8) and hope you get those little  itches sorted out to give a real professional impression also in this technical regard.

Thanks for your hard work

pls check again .. should be solved now!

Quote from: mudshark79 on February 01, 2015, 09:25:11 PM
While you are at it looking for the cert and stuff please also double check overall speed of the site, got some mixed results really, opening and trying the download link (checked from 4 different locations whereas it appeared reaaly slow from at least two). Maybe you can beef up server-provider side?

More serious: there are at least 5 HTTP500 timeouts for some font-files referenced + at least one javascript error. Also cross-browser testing shows the site isn't working in older IEs (9 to be specific - of course a pain for sure and really not a biggie in regard of importance but should be taken care of later).

So just a little nit-picking from my end  8) and hope you get those little  itches sorted out to give a real professional impression also in this technical regard.

Thanks for your hard work

yup thx for your input - will fix it soon !