iank
August 30, 2016, 3:21pm
291
Hi David
Thanks for your response and suggestions.
I fear I’m still encountering the same problem - even when I set up a new account. It’s very strange. The uploading just stops after 14 files - whether via Folder or individually. I haven’t reached the PUT limit (yet!).
Best
Ian
@iank are those the same 14 files each time?
Or any random 14?
what file type are they?
You should also see enough detail in the terminal to copy-paste the problem that suggests.
I have been lurking on this forum for a couple of years, and now finally this:
http://ice.icecream.safenet
Grinning from ear to ear!
5 Likes
let me know if this works for anyone:
http://boom.bigbang.safenet
not sure if it’s not working, or just not loading
Not loading in my browser FWIW.
1 Like
JBishop
August 31, 2016, 8:09pm
297
Probably because of this:
The new version of launcher enforces CSP headers which doesn’t allow java scripts and css to execute from the html directly. This is done to prevent XSS attacks.
If you can make the javascripts and css as separate files and link it to the html then the things should work fine.
2 Likes
@whiteoutmashups - re boom.bigbang.safenet is falling foul of the CSP
The new version of launcher enforces CSP headers which doesn’t allow java scripts and css to execute from the html directly. This is done to prevent XSS attacks.
If you can make the javascripts and css as separate files and link it to the html then the things should work fine.
http://dir.yvette.safenet/
Out of 436 PublicIDs guessed, fell 255 websites
with 98 sites going beyond the default
3 Likes
Should be fixed now, I took out the inline headers and made them separate CSS files. Updated link:
safe://boom.bigbang
1 Like
working on newest version of MaidSafe Pacman Vs Google Ghosts:
safe://pacman.bigbang
debugging…
_EDIT: If you wanna try it over clearnet / Git for now: tiny.cc/MaidSafeMan
JBishop:
Probably because of this:
The new version of launcher enforces CSP headers which doesn’t allow java scripts and css to execute from the html directly. This is done to prevent XSS attacks.
If you can make the javascripts and css as separate files and link it to the html then the things should work fine.
Would that also mean I can’t do things like:
<div style="background:blue; padding-top:20px;
padding-left:20px; padding-right:20px;
padding-bottom:20px; margin-top:20px;
width:600px;">
or explicitly just bans me from pure < style> & < script> tags with css / js in them?
I am pretty sure that’s just as bad. If you can inline CSS a website can do nasty things. Search for inline CSS vulnerabilities and you’ll see!
1 Like
JBishop
September 7, 2016, 10:06am
303
Inline style …
Much of it is like cooking or carpentry, did you try it?
I did, added a closing </div>
, sent it off, source is there but no trace of your blue element.
Yeah I can’t get the box to appear…
Probably one of the js scripts isn’t working from it’s separate file
JBishop
September 7, 2016, 3:30pm
305
Ok, an excuse to try @DavidMtl ’s new SafeEditor
Had to strip the style ‘attribute’ from the div-tag in the HTML and leave it ‘id’-ed like so:
<div id="bluerect"></div>
Like you, did move the CSS to a separate file, say “style.css” and refer to the ‘id’ of the div:
#bluerect {
background:blue;
padding:20px;
margin:20px;
width:600px;
}
And an instruction for browsers to load the new ‘stylesheet’ as well when opening the page:
<link href="./style.css">
This went between <head>
and </head>
in the HTML.
Test: now the blue element does appear … hopefully in yours too?
4 Likes
Yeah I tried that earlier but it didn’t make a difference when I uploaded to SAFE. I think it’s the javascript file
JBishop
September 7, 2016, 6:14pm
307
Ah, its for your Pacman-page. In that case, the corresponding line you have in there for the external style sheet differs from the one I was using …
http://dir.yvette.safenet/ on Alpha
Out of 1016 PublicIDs guessed, fell 477 websites
3 Likes
iank
September 21, 2016, 9:10am
309
Sorry for the delay in getting back to you. I’ve now nailed the problem. I had an empty favicon.ico file in the directory which the uploader couldn’t handle.
Thanks for your interest and support.
Ian
iank
September 21, 2016, 9:12am
310
Very sorry for not getting back to you sooner.
I’ve now nailed the problem. I had an empty favicon.ico file in the directory which the uploader couldn’t handle.
Thanks for your interest and support.
Ian