Redirect to subdomain not working when specifying http scheme

I’ve recently uploaded a website on a domain. Using the domain registrar (NameCheap) I’ve also applied a 301 redirect rule so that going to "@" (for example will redirect to

However, I noticed that if I specify the http scheme like so – I get redirected to, and get an ERR_CONNECTION_REFUSED error.

What’s the reason for that and how can it be fixed? Am I doing some things wrong?

I’ll mention that at first the 301 rule did not work when I specified to go to, and only after replacing the https with regular http did it work (although when visiting the site, I still see in the URL that it is in fact using https).

I am receiving a pluggable.php warning sign on my only http:// page

I just recently shared a link to my site ysing he http but instead of redirecting, i just displays this:

Warning: Cannot modify header information – headers already sent by (output started at /home/thecmltm/public_html/index.php:1) in /home/thecmltm/public_html/wp-includes/pluggable.php on line 1281

Warning: Cannot modify header information – headers already sent by (output started at /home/thecmltm/public_html/index.php:1) in /home/thecmltm/public_html/wp-includes/pluggable.php on line 1284

I have searched all over the web but they all talk about function.php or wp_configure.php but that is not what my problem is. I have tried editing the index.php but nothing is wrong with it.

Please help me. Thanks in advance!

Can a webpage differ in content if ‘http’ is changed to ‘https’ or if ‘www.’ is added after ‘http://’ (or ‘https://’)?

When I use the Python package newspaper3k package and run the code

import newspaper paper ='', memoize_articles=False) for url in paper.article_urls():     print(url) 

I get a list of URLs for articles that I can download, in which both these URLs exist


As can be seen, the only difference between the two URLs is the s in https.

The question is, can the webpage content differ simply because an s is added to http? If I scrape a news source (in this case, do I need to download both articles to be sure I don’t miss any article, or are they guaranteed to have the same content so that I can download only one of them?

I have also noticed that some URLs also are duplicated by adding www. after the http:// (or https://). I have the same question here: Can this small change cause the webpage content to differ, and is this something I should take into account or can I simply ignore one of these two URLs?

HTTP Request Smuggling Basics

I am currently trying to learn HTTP Request Smuggling vulnerability to furthermore enhance my pen testing skill. I have watched a couple of videos on Youtube and read articles online regarding it but still have a couple of questions in mind. Question:

  • What are the attack vectors of HTTP Req Smuggling (Where should I look)?
  • What is the main way to provide PoC to companies with high traffic? I know that HTTP Smuggling could possibly steal people’s cookie, can this be used for the PoC or is this illegal?
  • Can this or other vulnerability be chained together? (e.g. self-xss & csrf)

Thank you everyone!

How to decide to use, then how to use an http url in an email, explained to a five year old?

I’m terrified of clicking on links in emails, and yet a colleague insists I do.

When I receive an email in my gmail account that contains links of the form along with its password, apparently sent from someone I know and expect it from, and who has supplied the password for the link to their NAS right next to it, should I try to overcome my fear of clicking on links in emails and consider clicking on it as at least fairly safe? Should I instead copy it paste it in a new tab?

The idea is that the document is evolving so the link will provide the latest version, but should I insist the colleague email me the document directly?

tl;dr: Should I

  1. click url
  2. copy/paste url in new tab
  3. balk, request document be emailed each time

If possible, can an answer be written in simple language?

Cropped, blanked out screenshot from email I received in my gmail:

partial screenshot of emailed urls

How to send SQL or HTML data over HTTP without triggering WAF rules?

I’m working on securing an application that receives SQL and HTML-like information that is actually proprietry formulas in some cases, and parts of XML documents in other cases.

So the WAF thinks some HTTP requests are SQL or HTML injection attacks while they actually aren’t.

So how can I send these formulas and XML informaiton without triggering those WAF rules? I tried encoding the data but that didn’t work.

Are node.js, express,, localhost on http, and alike ACTUALLY secure? [closed]

I use localhost for learning more coding, and I keep wondering the same question over and over again when I use Node.js:

Is it really safe?

Many, many people might have asked this. I would naturally want to put SSL HTTPS encryption on it, but there isn’t really anywhere you can get it, even if it may be a bit overkill.

It feels like there should and could be some "protection" or "encryption" type package for npm or something.

I haven’t used Node.js or localhost it for sensitive information, but should I be worrying about this?