davej
-
Posts
3,988 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Events
Everything posted by davej
-
See http://www.w3schools.com/cssref/pr_border.asp
-
Perhaps resize? https://developer.mozilla.org/en-US/docs/Web/Events
-
A thirty day demo dated from the download or first-run date? Why wouldn't they simply download it again every thirty days?
-
Well, it's true that hackers are always writing new tools, and yes they can write browser plug-ins or entire browsers, but I think there are things that could be built into the standards for browsers that could improve password and session security for non-HTTPS websites (which is the majority of websites). For example a "man-in-the-middle" attacker can overcome public-key cryptography if he is already inserted during the initial meeting, but once I have used a website it can remember my public key and I can remember its public key and any possible "man-in-the-middle" is rendered harmless.
-
It should be... $sql= "INSERT INTO mytablename (title, body) VALUES (:title, :body)"; There is a PDO example towards the bottom of the page here... http://www.w3schools.com/php/php_mysql_prepared_statements.asp
-
I think HTML5 should have offered something to fix this situation. What we have now is a complete reliance on HTTPS certification.
-
Huh? Maybe... <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"/> <title>title</title> <style> </style> <script> window.onerror = function(a,b,c){ alert('Javascript Error: '+a+'\nURL: '+b+'\nLine Number: '+c); return true; } </script> </head> <body> <input type="checkbox" id="chk01"/> <br/> <input type="button" id="btn1" value="Toggle"/> <script> 'use strict'; function togglechk(id){ var chk = document.getElementById(id); chk.checked = (chk.checked == true)? false : true; }//end of func document.getElementById('btn1').onclick = function(){ togglechk('chk01');}; </script> </body> </html>
- 8 replies
-
- 1
-
-
- Javascript Checkbox
- after
- (and 8 more)
-
You need to carefully describe what you want, because it isn't perfectly clear.
- 8 replies
-
- 1
-
-
- Javascript Checkbox
- after
- (and 8 more)
-
I would first suggest that you fix the errors. https://validator.w3.org/check?uri=http%3A%2F%2Fwww.anatoliajournal.com%2Fatad%2F%3Fsayfa%3Danasayfa%26lang%3Dtr&charset=%28detect+automatically%29&doctype=Inline&group=0
-
This website was (perhaps) the first website... http://info.cern.ch/hypertext/WWW/TheProject.html Although apparently the exact 1990 original was not preserved, and this is a slightly later version. http://timeline.web.cern.ch/events/the-worlds-first-website-and-server-go-live-at-cern Although there seems to be some disagreements about the first website/webpage... http://www.todayifoundout.com/index.php/2010/05/the-first-website-ever-made/
-
When you created the CMS table what were the title and body columns declared as?
-
Because you have an extra curly brace in here... div#dlogo { { text-align: right; } Also you should stop using the border attribute (put it in the css) and start using the alt attribute.
-
Huh? So why not just write a function to do that?
- 8 replies
-
- 1
-
-
- Javascript Checkbox
- after
- (and 8 more)
-
I just installed everything separately. I'm not sure what the advantage is of the unified package. I guess the installation is a little simpler.
-
Everything related to security is normally done on the server. I myself think that is a little short-sighted, but that is what is done.
-
Install Apache and Php on your Win7 machine. https://httpd.apache.org/ http://windows.php.net/download/
-
You could download a text-editor that is known to support UTF-8. Look at Vim or Notepad++.
-
If that did not work then your file is not UTF-8.
-
Where is your loop? http://www.w3schools.com/PHP/php_mysql_select.asp
-
Try something simpler... <!DOCTYPE html> <html> <head> <meta charset="UTF-8"> <title>t</title> </head> <body> <p>Put some foreign characters here ... </p> </body> </html>
-
That looks a little messed up, but are you also saving the Php file in UTF-8 format?
-
To me it seems like a bad design, but that is the way things work. The client posts the username and password to the server and the server does everything related to security. To actually protect the login process you really need to use HTTPS.
-
Look at this thread for some simplified ideas... http://w3schools.invisionzone.com/index.php?showtopic=54439&hl=
-
You can use a technique to process a form in a more automated manner to generate values and totals, but it can get pretty messy. You have to do it all over in Php (or other server-side code) anyway because a hacker can modify the submitted form.
