• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
UT Shield
College of Fine Arts Web instruction
  • Welcome
  • About Us
    • WordPress & Drupal
    • Websites & Content Owners
  • Getting Started
    • Learn Best Practices for Web
    • Vocabulary Terms
    • Do you need a website?
    • Ways to Get a Website
      • Website Options On Campus
      • Initiate a Project with the Web Team
      • Outsource or DIY
    • Know Your Audience
    • Navigation & Menu Items
  • Requirements
    • Americans with Disabilities Legal Obligations
      • Alternate Text
      • Use of Color & Contrast
      • Link Text & Appearance
        • Non-Visible Link Context
      • PDF Files
      • Software Plug-in Link
      • Captions, Audio Description & Transcripts
        • webVTT Caption File
        • Caption Using Amara
        • Writing Captions & Audio Description
        • Video & Remote Communications
      • Additional ADA Issues
        • Accessible Social Media
        • Video & Remote Communications
    • UT Web Accessibility Policy
    • UT Web Privacy Policy
    • Records Retention – Backups, Archives and Revisions
    • College of Fine Arts Brand
    • UT Brand Guidelines
    • Information Security Office Policies
  • Best Practices
    • College of Fine Arts Communications Written Style Guide
    • Using a Rich Text Editor
      • Using an External HTML Editor
    • Links & URLs
      • Link Text & Appearance
        • Non-Visible Link Context
      • Absolute vs. Relative Paths
      • HTTP vs HTTPS
      • Anchor Links
      • Changing URLs
      • Shorten a URL for Marketing
    • Images
      • JPG vs PNG
      • Image Editing and Troubleshooting
    • Web Forms & Surveys
      • Create a Link to Pre-Filter a Web Form Page
    • Standards & Structure
      • Hierarchical Headers
      • Computer File Names
      • URL address names
        • UT Short Links Service
      • HTML
        • Common HTML Errors
        • Multiple Rows with Floated Images
        • Responsive Word Wrapping
    • Artificial Intelligence
    • Test & Evaluate
    • Wikipedia
    • Social Media & Networking
      • Accessible Social Media
    • RSS & Feeds
    • UT Austin Web Publishing Guidelines
  • Site Performance
    • Page Load Time
      • Fonts
    • Respond to a Variety of Devices
      • Telephone Numbers on Smart Phones
    • Analytics & Visitor Data
      • Outreach Campaign Link Tracking
        • Campaign URL Builder
        • Campaign Link Tracking Worksheet
    • Page Not Found Traffic
    • Tips to Increase Traffic
    • Optimize for AI Chat and Search
  • Site Specific Instructions
    • Instructions for COFA sites on University Blog Services WordPress
    • Instructions for COFA Drupal Kit sites
    • Instructions for COFA sites on UT Drupal Kit Managed

HTTP vs HTTPS

Last Updated August 2023

Terms and Definition: Hyper Text Transfer Protocol Secure (HTTPS) is the secure version of HTTP, it uses the the Secure Sockets Layer (SSL) protocol over which data is sent between your browser and the website that you are connected to. The ‘S’ at the end of HTTPS stands for ‘Secure’. It means all communications between your browser and the website are encrypted. An “SSL certificate” is necessary to create an SSL connection.

Website forms and other places you enter information into, should always use these security measures. If you ever see a scary message like, “There’s a problem with the websites security certificate” or “This connection is untrusted” do not enter secure information!

Browsers have moved toward practically requiring web sites to always use the secure protocol and will show the scary messages to website visitors, even if there is no information exchange through a form. For this reason, most websites now always use the secure protocol.

What you should know:

  • If the page is using the secure protocol all content included or embedded on the page, like images or iFrames, must also be secure.
  • For internal content, such as images and links to documents, use a relative link.
  • For embedded content, like iFrames, use https. Previous recommendations to use a “protocol relative” path (i.e. remove the http or https from the source code path, ex. src=”//www.youtube.com”) will still work, but is not current best practice.
  • If you are logged in and copy a URL to share, make sure to test it in a browser where you are not logged in to makes sure your audience will see the content as expected. If not, you may need to add or remove the “s” from the path before you share it.
  • Never enter secure information into a website that is not using the secure protocol or loads a scary message.

Primary Sidebar

Open Office / Co-Working Sessions

Second Monday of the month:
11 a.m. – 12:30 p.m.

Fourth Thursday of the month:
2 p.m. – 3:30 p.m.

Email us for the Zoom link.

College of Fine Arts WordPress Instruction
College of Fine Arts Drupal Instruction
Subscribe to our email list to receive periodic tips and resources for generating great digital content

Contact Us

The COFA Web team can be reached by emailing us at cofawebmaster@austin.utexas.edu


To view some links on this page you may need to download Acrobat Reader.

UT Home | Emergency Information | Site Policies | Web Accessibility | Web Privacy | Adobe Reader

© The University of Texas at Austin 2025