YES FOLKs - this REALLY works


    

:lol: 1-
Depending on how your browser is configured - putting this code in our address bar - changing the URL paramaters to match YOURS - will bring you INTO the files of your website

:lol: 2-
Right Clicking on the HTML file of your choice - select "OPEN"


then "VIEW SOURCE" for the opened html file

:lol: 3-
make your changes and save it to your harddrive - desktop - A drive etc...


:lol: 4-
Select the HTML ICON and right click and select "COPY"

:lol: 5-
Open up your FTP window and either right click or edit--> paste

:lol: 6-
or - Add the FTP shortcut and DRAG and DROP from the same folder


VOILA' you will have automacally updated your WEB PAGE

Dani AI

Generated

That browser trick can be convenient for quick one-off edits, but it is fragile and risky. shows it works in some setups, and is right that full FTP clients make multi-file work far easier. However, embedding credentials in a URL or relying on a browser FTP view exposes passwords to browser history, server logs, proxies, referer headers and (if published) search-engine caches — exactly the kind of leak warned about. Many browsers and hosts also treat userinfo-in-URLs inconsistently, so the method may stop working without notice.

Use a secure, reproducible workflow instead:

  • Connect with SFTP or FTPS (encrypts credentials in transit). If your host only offers plain FTP, ask them about SFTP or use a client that supports explicit TLS.
  • Edit locally in a proper text editor (Notepad++ is a good lightweight choice noted earlier) and keep a dated backup copy before uploading.
  • Upload with a client that supports drag/drop and remote editing (this is what was suggesting). Clients also let you set correct permissions (typical web defaults: 644 for files, 755 for directories).
  • Verify the live page with a hard refresh or by checking headers to avoid stale-cache confusion.

Quick verification examples:

# test SSH/SFTP connect (example)
sftp user@example.com

# check HTTP headers to confirm you see the new file
curl -I http://example.com/path/to/file.html

If the browser-address approach is tempting for speed, limit it to throwaway accounts and never paste credentials into public pages. For real sites, use an encrypted transfer method, versioned backups, and a client with remote-edit features to stay efficient and secure.

Recommended Answers

All 4 Replies

I'm confused as to why this is spectacular???

With a program such as cuteFTP you could make your entire website and drag and drop it acroos sending 5 files at a time (not sure how many acctualyl i havent used cuteftp for a while)

i dunno how safe that way is. ive seen many people get sites passwords and usernames by typing "@domainname.com" in google, sometimes google caches that little bit and will display it in the search results. i know thats a common way to steal porn site passwords at least..

Member Avatar for Member #2466

http://winscp.sourceforge.net/eng/

Much better...drag and drop just like what you're talking about...but can go through proxies and firewalls and is secure.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.