Have subdomain forward to external site [on hold]

I’m looking for a way to have a subdomain forward to an external site. Like this:

https://foo.bar.example -> https://www.dropbox.com/request/jdhfj75sdW0W1XDwO7l

What’s the easiest way to do this?

Is it easier using the webserver that runs on the domain and do it like this: https://bar.example/foo/index.html

What would go into the index.html so that it would forward to Dropbox?

1 EDU post from Strong .ac.id SubDomain for $6

Post your article permanently on an authentic .ac.id blog! Informative articles and links placement on edu categorized domains can greatly help your SEO. The rules: I have the right to refuse any submissions that are deemed as unacceptable content. I will not accept any content regarding pornographic, MLM, cash, loans, gambling, dating or drug related material. I can provide you with 350 word free article or you can provide the article with term bellow: 1: You provide the article or guest post. Articles must pass copyscape. 2: Poorly written material or poor grammatical errors will be rejected. 3: Only links to quality piece of content on your website or a tutorial. 4: Anchor text must be relevant to the page you’re linking to. 5: The number of back-links allowed is based on article length: 200+ words = 1 link 500+ words = 1-2 links 700+ words = 1-3 links All approved content submitted are guaranteed permanent placements. Questions? Feel free to ask! FAQ: How often will the site be re-indexed with google? The site is re-indexed twice per month. What are the domain metrics?

by: quthubm
Created: —
Category: Site Link Sales
Viewed: 206

What is the most secure way to store cross subdomain cookies

I am working for a company we will call “Company x”. This company has a domain companyx.com. They have a cloud platform that manages things like SSL, but in order to do this you are required to use that domain. There are 3 apps app1, app2 and app 3 that have the following urls…

app1.companyx.com app2.companyx.com app3.companyx.com 

These are need to use stateless auth since they are highly scalable. All of these “share” the same session (JWT) using a cookie that is http-only and secure but because there is no way to create a subdomain are all using the companyx.com domain for their cookie.

The security team has pushed back saying that we are “providing the cookie” to the whole domain. This seems a little weird to me since the company also controls the core domain but I also know there is a lot of focus today on internal as well as external threats.

So is there a way to structure the cookie so that app1, app2, and app3 have access but app4 does not? Is there a more secure way than just using the core domain? How big of a threat is this really?

is it a vulnerability to redirect to any subdomain? similar to Open Redirect

i found a website that has the parameter post_login_redirect= i can change to any existing and non-exisiting subdomains, but there is no posibility to redirect to another domain. The redirect occurs after the user logs in.

For example:

we have sub.domain.com and we can change to anything if we respect the domain.com. so we can redirect to a.b.c.b.domain.com even if that subdomain doesn’t exist, it will redirect anyway. But we can’t redirect to a.hello.com

This is not an open redirect issue, because we can only redirect to subdomains that we don’t own.

Is there any possibility to chain this or make this a real vulnerability?

NGINX, subdomain using server blocks doesn’t work

I would like to use nginx to redirect user from domain.com:3001 to sub.domain.com. Application on port 3001 is running in docker container, I didn’t add any files in directory sites-available/sites-enabled. I have added two server blocks (vhosts) in my conf.d directory. In server block I set $ upstream and resolver according to record in my /etc/resolv.conf file. The problem is that when I test in browser sub.domain.com every time I receive information that IP address could not be connected with any server (DNS_PROBE_FINISHED_NXDOMAIN) or 50x errors.

However, when I run curl sub.domain.com from the server I receive 200 with index.html response, this doesn’t work when I run the same command from my local PC. Server domain is in private network. Have you any idea what my configuration files lack of?? Maybe there is some issue with the listen port when app is running in docker or maybe there is something wrong with the version of nginx? When I installed nginx there was empty conf.d directory, with no default.conf. I am lost…

Any help will be highly appreciated.

Here is my configuration files: server.conf:

server  {     listen       80;     listen       443 ssl;     server_name  sub.domain.net;      #charset koi8-r;     #access_log  /var/log/nginx/host.access.log  main;      ssl_certificate /etc/nginx/ssl/cer.crt;     ssl_certificate_key /etc/nginx/ssl/private.key;      #set_real_ip_from;     #real_ip_header X-Real-IP;     #real_ip_recursive on; #    location / { #        root   /usr/share/nginx/html; #        index  index.html index.htm; #    }      location / {         resolver;         set $  upstream;          proxy_pass $  upstream;          proxy_set_header X-Forwarded-Host $  host;         proxy_set_header X-Forwarded-Server $  host;         proxy_set_header X-Forwarded-Proto $  scheme;`enter code here`         proxy_set_header X-Forwarded-For $  proxy_add_x_forwarded_for;         proxy_set_header Host $  host;      #error_page  404              /404.html;     # redirect server error pages to the static page /50x.html     #     error_page   500 502 503 504  /50x.html;     location = /50x.html {         root   /usr/share/nginx/html;     }      # proxy the PHP scripts to Apache listening on     #     #location ~ \.php$   {     #    proxy_pass;     #}      # pass the PHP scripts to FastCGI server listening on     #     #location ~ \.php$   {     #    root           html;     #    fastcgi_pass;     #    fastcgi_index  index.php;     #    fastcgi_param  SCRIPT_FILENAME  /scripts$  fastcgi_script_name;     #    include        fastcgi_params;     #}      # deny access to .htaccess files, if Apache's document root     # concurs with nginx's one     #     #location ~ /\.ht {     #    deny  all;     #} }  nginx.conf  #user  nginx; worker_processes  1;  #error_log  /var/log/nginx/error.log; #error_log  /var/log/nginx/error.log  notice; #error_log  /var/log/nginx/error.log  info;  #pid        /var/run/nginx.pid;  include /etc/nginx/modules.conf.d/*.conf;  events {     worker_connections  1024; }   http {     include       mime.types;     default_type  application/octet-stream;      #log_format  main  '$  remote_addr - $  remote_user [$  time_local]     #                  '$  status $  body_bytes_sent "$  http_referer" '     #                  '"$  http_user_agent" "$  http_x_forwarded_for"';      #access_log  /var/log/nginx/access.log  main;      sendfile        on;     #tcp_nopush     on;      #keepalive_timeout  0;     keepalive_timeout  65;      sendfile        on;     #tcp_nopush     on;      #keepalive_timeout  0;     keepalive_timeout  65;     #tcp_nodelay        on;      #gzip  on;     #gzip_disable "MSIE [1-6]\.(?!.*SV1)";      server_tokens off;     include /etc/nginx/conf.d/*.conf; }  # override global parameters e.g. worker_rlimit_nofile include /etc/nginx/*global_params 


Does Facebook use any other CDN apart from Akamai? Encountered fbcdn.net subdomain that does not belong to Akamai

I received a notice from my third-party firewall application (Little Snitch) that when I had Facebook open, my browser (Chrome 46.0.2490.80 on El Capitan 10.11.1) was attempting to connect to “scontent.fper1-1.fna.fbcdn.net” and “scontent.fmel1-1.fna.fbcdn.net”. Having never seen these particular variations on the fbcdn domain before despite daily use of Facebook and having used LS for a while, it was a little suspicious to me.

Looking up the IP addresses ( and respectively) point to Internode, an ISP located in Adelaide, Australia (I live in Australia, but not Adelaide) and AFAIK, Facebook does not use their CDN and I don’t think Internode even provides such services.

But the domain is fbcdn.net. right? And if that’s so, which is legit domain used by Facebook for content/cookies etc, even if the IP addresses don’t resolve to Facebook or Akamai, it should be fine? Nothing suspicious?

Forward GoDaddy subdomain to a different port on the same server (reverse proxy)

So here is the situation: I purchased a domain with GoDaddy (Jbc.ca) GoDaddy forwards to my no-ip domain currently as I have a dynamic IP address (however it does not change that frequently- so I could in theory have it forward directly to my IP address).

Now here is where it gets a little more complicated. I run a web server (Apache) on port 80 which is displayed when you visit (jbc.ca) I also have several other services that run on the same system: Plex- port 32400; Tautulli on port 7777; Ombi on port 5000; Lidarr on port 8686, Remotely Anywhere PC Access on 7000 and a separate Web Server (Microsoft IIS on port 9024).

Currently to access any of these services other than port 80 I have to do as follows: “http://Jbc.ca:Port#” ; so for example to access Ombi I have to type in http://jbc.ca:5000.

What I would like is to have my domain with subdomains for each port- so for example ombi.jbc.ca would in theory load port 5000 on the server, but would display ombi.plex.ca instead of redirecting and exposing the port number. Ra.jbc.ca would load port 7000 and so on…

I have read that this can be done with reverse proxy via apache or nginx (as I am running mamp pro for my main server) as well as IIS, however I have no clue how to accomplish this as to what needs to be changed/added on the server, which server would be best to accomplish this as well as what I’d have to modify on my GoDaddy domain.

Hopefully someone can help as I am totally stumped at this point.

Thanks in advance.