Ah, there we go. Orders of magnitude less than. I feel safer already. :java: TTFN - Kent

Red Kipling wrote: upload a files in my website I have this javascript code integrated to show the progress of upload But the issue is that this bar has value of 100% before the upload is completed How can i resolve this See what happens if you replace this code: xhr.upload.onprogress = function (event) { //code }; ...with this xhr.upload.addEventListener("progress", function (event) { //code }); Although your code is correct, try using the addEventListener method to see if that makes any difference. I believe that event listeners need to be assigned before the xhr's "open" method is called.

thanks you

charlieg wrote: I recommend watching as many of these videos as possible: Toodaloo! - YouTube[^] Ahhh, that's it - thanks a million. I bumped into a few of them the other week and laughed my backside off. Then I couldn't remember what the channel was called and since I'd been watching in incognito mode, had no history. Soon as I saw the University of North Texas mug, I knew they'd be a hoot. :laugh:

Member questions & answers[^] A link to his blog as a "solution" to an already-solved question. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

I realise I've come to this post a long time after the request, but thought I'd still provide an actual way forward, possibly even the solution if one is still required. Or maybe it will serve some useful purpose for another poster with a similar need. If you understand the regex you have provided you will understand the first 2 sections are only a lookahead to identify the requirements are met, they don't actually consume any characters. The .{7,}$ is the part which grabs the password and at the moment it will grab any character (denoted by the DOT character). So it's here where you could do the final verification. What needs to happen is that the DOT changes to the "allowed" characters which exclude the space (and/or any other characters). I don't do PHP regex but I would think replacing the DOT with something like \S or [^ ] or even [[:^space:]] would be appropriate. By removing a character from the allowed group, if the removed character is encountered the regex will fail. So no password is selected. It could even be done with another lookahead and I think that could be (?=\S{7,}). If using the lookahead, then no need to change the DOT character for my other options. Some background info: \S is any character except whitespace which includes [ \t\r\n\v\f]. This is a capital S, which is the negated \s, so opposite of what \s means in PHP regex (whitespace). [[:^space:]] is a negated PHP class, the ^ denotes NOT what follows. Terry

Spammer terminated. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

I didn't read the replies first, but will post my response to the question. I started working on a customers PHP project in Sept 2020, which was written in PHP 4.2 between 2004 to 2010 by some Chinese students from China. They did a terrible job, and everything you can possibly do wrong they did wrong. I can't even read the code. Anyways, it was so bad, that I told the customer that they really need to sort of start from scratch again. Why I chose pure PHP 7.4 for them. Drum roll please .... Because of time and money ... So many of the new technologies are constantly being updated so fast, that it's hard to keep up with the changes. PHP 7.4 is still that Swiss Army knife that can do almost anything, and PHP doesn't bug you to update code, or doesn't require a team of skilled software engineers to maintain over decades. Once you write it and deploy, it can run for a long time without more time and money. I can move on to the next project, and the customer can use their new app for years to come, and pass that app to their next generation of children that will take over the business when they come home from College or University. Our economy in the US has a strong service sector, comprised of small business owners with family involved, and have become generational now spanning their services across decades of time. I look at pure PHP 7.4+ from an economic point of view, and not from a superior technology point of view, considering time, labor, capital investment and maintenance being more stable and predictable across good times and bad. I don't agree with PHP Laravel as being a framework built on PHP, but opted for pure PHP, in which I was able to build a near MVC type of Web Application using modern objects and smarter HTML views with the objects, and include robust HTTP request and response handling, and robust security features. I have no regrets in my decision for my customers path forward, and I'm very happy with the results. Well that's my argument for PHP. May not be what you were expecting to hear or read, but I hope it satisfies your thirst to know why. If it ain't broke don't fix it Discover my world at jkirkerx.com

You'll be surprised, like taking a stroll with grandma. :laugh: