Syndicate content

HTTPS

Hyper Text Transfer Protocol Secure—The protocol used by browsers to communicate to web servers securely. The security is done with similarly to SSH. The transfer uses FTP like commands, but only one connection. Since HTTP 1.1 it is also possible to reuse the same connection for multiple files (pages, images, videos, etc.)

Useful online network tools

I'm starting this page and hope to think about it again at a later time when I find additional tools... but as I have network problems I often need these types of services to make sure I can get the information I need.

For more Network stuff, click on the Network tag!

What is your IP address?

Check your current IP address from your browser:

http://alexis.m2osw.com/nvg510/my-ip.php [Super clean version!]

https://www.whatismyip.com/ [More advance and with ads...]

What is my DNS?

This one is for people who setup a DNS to make sure that it can accessed from all over the world. It ...

Restore Firefox warnings when viewing non-secure data on a secure page

One thing that I quickly do on my browsers is turn off warnings about non-secure data when browsing secure pages (with HTTPS .)

It's rarely a problem and with all those features you like to have (Facebook, Twitter, AddThis, ShareThis, Google Plus, and othe fun widgets...) it's hard to avoid. Actually, many times the problem lies in one of these scripts and thus you cannot just fix your website. Without that 3rd party script owner fixing their code, it just won't work at all.

Now, once in a while I work on a customer website and they really want to have a 100% clean slate. Thus,

Upgrade from Ubuntu 9.10 to 10.04

Today I did an upgrade of a server from 9.10 to 10.04. We were on a server version before upgrading to 9.10 but we could not directly upgrade to 10.04 (working upgrade paths are very specific; see a list here: https://help.ubuntu.com/community/UpgradeNotes )

The most surprising part was the python script at the end.

  /usr/bin/python /tmp/unique-folder/lucid --mode=server --frontend=DistUpgradeViewText

The command line itself is not specifically strange. However, the behavior at the end of the script is a bit strange, mainly because I hadn't see it before. Last time the upgrade was

[info] Subsequent (No.7) HTTPS request received for child 0 (server secure.m2osw.com:443)

The other day I was looking for an error in Apache error logs and I noticed an error that was repeated over and over again:

[info] Initial (No.1) HTTPS request received for child 5 (server secure.m2osw.com:443)
[info] Initial (No.1) HTTPS request received for child 0 (server secure.m2osw.com:443)
[info] Initial (No.1) HTTPS request received for child 7 (server secure.m2osw.com:443)
[info] Initial (No.1) HTTPS request received for child 2 (server secure.m2osw.com:443)
[info] Initial (No.1) HTTPS request received for child 4 (server secure.m2osw.com:443)

Notice the pattern? Only one

POSTing multiple files over HTTPS

I've been trying to send a POST to Apache 2.x using cURL. In itself, that's very easy to do. However, I run modsecurity and when cURL sends a POST that's too large, it actually decides to break the transfer down using an Expect: 100-continue header. That in itself sound good.

Some people said that you could override the Expect by adding the curl option to add a header like this:

  curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));

This sounds all nice, however, it only removes the header from the request, it does not prevent the errors with modsecurity. Not only that, the curl header

Syndicate content Syndicate content

Diverse Realty

Diverse Realty Team

Want a New Home?
Want to Sell Your House?

Call Alex at
+1 (916)
220 6482

Alexis Wilke, Realtor
Salesperson
Lic. # 02024063

Cory Marcus, Broker
Lic. # 01079165

     

Terms of Site Index

Find the page/content you are looking for with our index.