At present I have a working DropzoneJS implementation where a user can select multiple images and upload them. There is a parameter parallelUploads which seems in practice to determine how many images can be uploaded at once, for example when the Select Files dialog is opened if the user selects 10 files, but parallelUploads:5 then only the first 5 images will upload successfully and the remaining 5 will be ignored, and those 5 images are sent via a single HTTP POST request.
What I would like to be able to do is configure it so that there is no limit to how many images are uploaded, but that they are uploaded in batches. For example, if a user selects 30 images, I would like them to all be uploaded successfully, either with 1 image per HTTP POST request or with a defined number per HTTP POST such as 5. If I set parallelUploads:30 then the server requires a vast amount of memory to try and do server-side processing on 30 images in one go and this doesn't seem to be a great solution.
How can I configure it to launch a separate HTTP POST request per image or for just a defined number of images at once without capping the number of images being uploaded in one action by the user?
<link rel="stylesheet" type="text/css" href="dropzone.css" media="all" />
<script type="text/javascript" src="dropzone.min.js"></script>
<div id="pnlPhotoThumbnails"></div>
<div class="clearfix">
<form id="frmUpload" method="post" enctype="multipart/form-data"
action="photo-upload.json" class="dropzone">
<input type="file" name="photo" id="photo" />
</form>
</div>
<style type="text/css">
#frmUpload input[type=file]{display:block;height:0;width:0;}
</style>
<script type="text/javascript">
function RefreshPhotos(){ $('pnlPhotoThumbnails').load('photo-thumbnails.php'); }
$(function(){
$('frmUpload').dropzone({
acceptedFiles: '.jpg',
parallelUploads: 5,
init:function(){
var hDropzone = this;
this.on('success', function(){ RefreshPhotos(); hDropzone.removeAllFiles(); });
}
});
});
</script>
Note: Above is an example code similar to the implementation I have, though I've edited it somewhat to make the question general rather than specific to my project, and hopefully with sufficient code to give an idea of how it works so bear in mind its not complete and functional from just this snippet! photo-upload.json would be a server-side script to process the file upload and return a JSON succcess/error response, photo-thumbnails.php would return HTML with <img/> tags for each of the photo thumbnails.
It turns out the following configuration will solve this, when in this specific case it will allow up to 100 files to be uploaded in one user action, but with an individual HTTP POST request for each image upload.
As of DropzoneJS version 4.0, it does not appear possible (correct me if I'm wrong) to set the number of files allowed to be uploaded in one go to unlimited, or to define a number of images to batch together, they are either all uploaded together or all uploaded separately:
parallelUploads: 100,
uploadMultiple: false
I am from electronics background so don't have good knowledge in designing webpages. I am doing an ethernet project and for that I need to make a webpage but before that webpage I also need to make a login authentication webpage. I somehow managed to do it using HTML JAVASCRIPT but the problem is anyone can see the username password by viewing the page source.
I am having hard time making authentication. I have basic knowledge of HTML and JAVASCRIPT but ready to learn. All I can find on google is login templates but I don't even know how to use them.
Can anyone give me an example or point me to some good links.
HTML and Javascript are interpreted on the client side. For login purposes, it is the server side code that is commonly used to verify the credentials - simply because that fact that you are already aware of - with a simple client side implementation, you can see the credentials in source code, server side is also easier to work with, once you understand it, it is more flexible for further development, it is more secure, and it is really used everywhere for this task.
It is a good idea to use PHP, ASP, Ruby (or any other server side language) for this. If you do not want that, you need to make it hard for the user to read the credentials from the source code.
In order to do that, you can use various methods like cryptography or obfuscation. Cryptography is highly recommended over obfuscating as it provably adds more security to your application. Obfuscating basically means that you change the source code in a way that it is hard to read - you add functions that encode strings, so that your "password" can not be spotted on the first sight. However, obfuscation can always be bypassed, and usually quite easily with a good debugging tools.
So, let's go with cryptography. What you are looking for here is using one way hash functions. You have plenty to choose from - MD5, SHA1, SHA256, ... each provides different level of security. SHA256 implementation in Javascript is an example you can use. There are many other libraries and examples for this, so just use Google and find the one that you like.
Now, what to do with it? Say you have sha256() function that accepts a string and returns its hash as a string. For each user and password you have, you precount SHA256 hash of string "user + password".
Say, you want your username to be "Pedro" and password for this account is "MyPassword".
You precount the hash of "PedroMyPassword" - e.g. with with online hashing tool. You can see the its SHA256 hash is
40be6e939eedf018b2b846e027067dcb006585a2155ce324f1f2a6a71d418b21
This hash is what you put into your Javascript code.
When the user enters their user and password, you call your sha256 function on "username + password" and you compare it to your precounted hash.
Note that you have to select really strong password, otherwise certain attacks (such as dictionary attack) would be easy to use to break your hash.
The problem is now, that you did not specify, what you want to do next. For example, you might want to redirect authenticated users to next page, but here you have the same problem again - if you have redirection in Javascript to "secondpage.html" in your code, someone could just skip the authentication and navigate to this second page directly.
What you can do in this case is that you name your second page as
40be6e939eedf018b2b846e027067dcb006585a2155ce324f1f2a6a71d418b21.html
i.e. the hash of your user+pass string. In this variant you do not put the hash in the code at all. The web server will just return error 404 for all users that fail to authenticate. For example, if someone attempts to use "Pedro" with "123456" as password, the SHA256 would be
3bac31720fdd4619ebe2e8865ccc0dc87eb744f3f05f08c628bb9217a77e4517
and if you redirect them to
3bac31720fdd4619ebe2e8865ccc0dc87eb744f3f05f08c628bb9217a77e4517.html
it won't exist, because your second page file is called
40be6e939eedf018b2b846e027067dcb006585a2155ce324f1f2a6a71d418b21.html
You would need to create these second pages for each user/pass combination. You could then put a simple redirection code to the real second page.
But make sure you are using HTTPS protocol, otherwise, the second pages would go through the wire unencrypted ...
This all will work, but still, I highly suggest, you consider the server side way.
In my previous answer I was using client side technologies thats why the username and password was not safe and hidden if we check the page-source.
Now,we will use server side technology, for this you need web-server package such as WAMP,XAMPP etc
Download and install one of these packages.(if you have one of these two, then its well and good)
I am using XAMPP so I will explain with XAMPP.
If you have successfully downloaded XAMPP,
then look for the htdocs folder in XAMPP folder. Mine is "C:\xampp\htdocs"
copy the below code and create new php fileand Save this file as login.php in htdocs directory.
Here is php code.
<?php
$usr="root";
$pwd="root";
if(isset($_POST['username']) && !empty($_POST['username']) && isset($_POST['password']) && !empty($_POST['password']) ){
$username=$_POST['username'];
$password=$_POST['password'];
if(($username==$usr) && ($password==$pwd) ){
echo '<br>login successfull';
}else{
echo '<br>login unsuccessfull';
}
}else{
echo "<br>Connot be left empty!";
}
?>
ok!! Now Create a simple HTML page containing login form and save this as login.html
Here is the HTML code
<html>
<head>
<title>Login</title>
</head>
<body>
<form action="login.php" method="POST" align="center">
<br>
Username:<input type="text" name="username"><br><br><br>
Password :<input type="text" name="password"><br><br>
<input type="Submit" value="Submit">
</form>
</body>
</html>
Now, Goto browser->Type http://localhost/login.html and run
Insert Username and password as root.
I am assuming you have basic knowledge of php, if not go through it, its is very easy and also read about HTTP requests
GET
POST
<html>
<head>
<title>Login paget</title>
</head>
<script type="text/javascript">
function display(form){
if (form.username.value=="root") {
if (form.password.value=="root") {
location="page2.html"
} else {
alert("Invalid Password")
}
} else { alert("Invalid Username")
}
}
</script>
<body >
<form >
<input type="text" name="username" /><br><br>
<input type="password" name="password"/><br><br>
<input type="button" value="Login" onClick="display(this.form)"/>
</form>
</body>
</html>
Hello I have created a login page for you using html and Javascript. The Username and password are root.
You see if you input correct username and password then the page directs to page2.html and this will show you
This webpage is not found
ERR_FILE_NOT_FOUND
so what you have to do is replace page2.html with your next page name.
You can't really have a secure authentication system using JavaScript and HTML alone.
I would suggest Basic HTTP authentication on your server instead, as it is much more secure (not perfect by any means, but at least employs a standard server-side method of access control).
If you must implement something in JavaScript, you could do a password only scheme based on the name of a hidden directory. Something like the following (note this is untested so will need some tweaks):
(Code borrowed and adapted from this question)
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></script>
<script>
$(function() {
var url = "some_url";
$.ajax(url,
{
if (statusCode == 200) {
document.location.href = url;
}
else {
alert('Incorrect password')
}
}
});
});
</script>
<input type="password" />Login
The code should be finished so that the function is called when the button is clicked. So if the password is foo, you set a directory on your website called foo, and if the JQuery JavaScript detects that the entered password matches a directory name (e.g. /foo/), then the user is redirected there. Therefore you'd create a /foo/index.html in order to take care of the user's logged in session.
Note that this is the most secure thing you can do with JavaScript and HTML alone and it suffers from the following vulnerabilities.
It requires that the URL be kept secret, although this can be leaked by the referer header, by browser history and server/proxy logs.
Once a user is logged in, they are always logged in (they could bookmark the logged in pages)
There is no easy way to revoke a password.
There is only one password.
Anyone with access to view files on the server could view the directory structure and learn the password.
The URL may be leaked by analytics tools.
Assumes directory browsing on your server is disabled (or that there's a default page in the private page's parent directory).
In any case, always protect your server with TLS/SSL. My recommendation is to properly create a user authentication system using the advice from OWASP. The above shows only what's achievable in basic HTML (not much). However, it is better than exposing the password within client-side files.
just try out this code
-
function validate(){
var username = document.getElementById("username").value;
var password = document.getElementById("password").value;
if ( username == "username1" && password == "password1"){
alert ("Login successfully");
}
else{
alert("Invalid username or password");
}
return false;
}
<html>
<head>
<title>Javascript Login Form Validation</title>
<!-- Include JS File Here -->
<script src="js/login.js"></script>
</head>
<body>
<div class="container">
<form id="form_id" method="post" name="myform">
<label>User Name :</label>
<input type="text" name="username" id="username"/>
<label>Password :</label>
<input type="password" name="password" id="password"/>
<input type="button" value="Login" id="submit" onclick="validate()"/>
</form>
</div>
</body>
</html>
We're trying to integrate PayPal Adaptive Payments,
This is how our form looks like:
<form class="standard" action="/our-controller" method="post" target="PPDGFrame">
<input type="image" id="submitBtn" value="Pay with PayPal" src="https://www.paypalobjects.com/webstatic/en_US/btn/btn_checkout_pp_142x27.png">
<input id="type" type="hidden" name="expType" value="mini">
</form>
<script type="text/javascript" charset="utf-8">
var embeddedPPFlow = new PAYPAL.apps.DGFlowmini({trigger: 'submitBtn'});
</script>
As you can see we are not providing payKey the reason for that we don't want to make API calls on each page view so we are trying to first redirect to our controller where payKey is fetched and redirect to the actual PayPal checkout page.
But we are getting this constantly:
To help protect your account, we logged you out. Click the refresh button in your browser window to log in again and start your transaction over.
Is there any way to achieve our goals? Because if we are providing payKey in input, it works find, but not with our workflow.
I am using Lazarus I have an app with webbrowser component on it that logs into a website loads a page as below (see html code below), and fills in different inputs. The last input is a file to upload. I would like my app to "click" Browse, select a file i want to, and Open. After that I could do a post the form OR just upload the file and carry on.
1
I have the following html code on the site:
<td align="left" class="RequiredInput">File:</td>
<td class="datafield">
<form name="frmMain" id="frmMain" action="upload.asp?step=2&output=1" method="post" enctype="multipart/form-data">
<input type="file" name="filename" id="filename">
</form>
I tried executing JS from my app : document.getElementById('filename').value = 'C:\x.csv'
2
I tried using the following code HttpPostFile from synapse:
uFileName := 'C:\x.csv';
uStream := TFileStream.Create(uFileName, fmOpenRead);
uList:=TStringList.Create;
if HttpPostFile('upload.asp?step=2&output=1', 'filename', uFileName, uStream, uList) then
ShowMessage('OK');
It did nothing at all (I followed the activity of the app with Fiddler)
This is a known problem, and there is a solution, but you're going to have to convert it from ะก# to Delphi.
Another possible solution is to upload the file using URL Moniker APIs. The upload will then happen on the same session the WebBrowser control is already using. There is an MSKB article:
How To Handle POST Requests in a Pluggable Protocol Handler
The POSTMON.EXE sample linked to the article has disappeared from Microsoft website, but still can be found here.
i need to set on my web page a upload form for videos and i want that this videos are sent to my mail.
i found this code
<form name="myWebForm" action="mailto:annie.etoile#gmail.com" method="post">
<input type="hidden" name="MAX_FILE_SIZE" value="10mb" />
<input type="video" name="uploadField" />
<input type="submit" value="Send">
</form>
But when i press on "Send" it opens my mailing software, it doesn't send autmatically to me the video.
Maybe there's something wrong in the code?
It "opens your mail software" because that's exactly what it's being told to do here:
action="mailto:annie.etoile#gmail.com"
When you say you want it to "upload"... Where do you want it to go? If you want to send it to the web server then you need some server-side resource which can receive it. For example, if you have a PHP page which accepts the file upload, you'd change your form action to that page:
action="fileupload.php"
Then you'd have server-side code in that PHP file to accept the uploaded file and do whatever you want to do with it. (Including mail it to you.)
It doesn't have to be PHP on the server-side code, any server-side language/framework/environment/etc. can do the job. The point is that you'd need something there. If all you have is client-side code (which is all you have in the question) then the mailto: action is about as good as it's going to get.