Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
The website is reachable by host name but not by the ip adress specified in the A record. The DNS successfully resolves the request to the same ip specified in the A record.
Postman tells me: Error: Hostname/IP does not match certificate's altnames: IP: [...] is not in the cert's list.
Background: I have connected a Firebase application with a existing Domain. Firebase has generated a certificate for this website.
There are not enough IP addresses for all web sites to have a unique IP address. Firebase Hosting makes everyone's sites share the same IP address, and is able to distinguish requests for sites using the HTTP Host header from each request. This means the Host header is required. Postman will add that for you automatically if you use the domain name of your site, but it would have no idea what to use if you just provide an IP address.
See also: What is http host header?
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Clients are connecting to private servers using OpenVPN, currently using raw IPs (172.X.X.X) but I would like to point more user-friendly subdomains (something.ourdomain.com) to those private IPs
Key is to
Not make our private topology public, so binding subdomains to a public DNS is not an option
Be able to push new settings to all clients efficiently, so modifying local hosts-files whenever a private IP updates could potentially be cumbersome
Not tie the routing to a specific local hardware, so doing the routing on say e.g. our office router is not really an option
Any suggestions how to achieve this considering the above points? Set-up a private DNS? Do the routing in OpenVPN?
1) Set-up private DNS server(s)
2) Push DNS server to your OpenVPN clients by addding
push "dhcp-option DNS 172.X.X.X"
to your OpenVPN server configuration (where 172.X.X.X is private IP address of your DNS server)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I understand that the job of IP in the TCP stack, when dealing with an outgoing message, is to resolve an IP address from a host name and add this address as a header.
Is this process that IP goes through equivalent to using a tool like nslookup for a given hostname?
Your understanding is incorrect. IP doesn't know anything about device names, it only deals with IP addresses.
An application can query a DNS server or a hosts file to resolve a name into an IP address. This must be done prior to using IP to forward a packet since IP can only use an IP address. Tools, like you mention, and other applications, such as browsers, query a DNS server (requires you have the IP address of a DNS server configured) or use a hosts file to resolve the name to an IP address.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I have Mikrotik router board,
I want to forward all site request to an IP address of specific site, in some hours of day
For example a.com forward to 188.158.x.x
Can any one help me?
using web proxy to forward http request to web proxy server Address
/ip proxy
set cache-administrator="Mehdi Haghshenas" enabled=yes max-cache-size=none \
parent-proxy=0.0.0.0
/ip proxy access
add action=deny dst-address=!x.x.x.x redirect-to=x.x.x.x
x.x.x.x is the server want to forward to
then you must add nat to forward http request to proxy server using
/ip firewall nat
add action=redirect chain=dstnat disabled=yes dst-address-list=!LocalIP dst-port=\
80 protocol=tcp src-address-list=LocalIP to-ports=8080
/ip firewall address-list
add address=192.168.0.0/24 list=LocalIP
add address=192.168.1.0/24 list=LocalIP
Just write a script which redirect all HTTP traffics to specific IP address and use routerOS scheduler to execute this rule in a specific time of the day/night, then write another script to remove that rule in another time. If you need sample just tell.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
We are running a Java based web-application, and were in the process of updating the site from http:// to https:// (by installing SSL cert),but encountered issues with bringing the site online.
On further analysis, we found that the port 443 was being blocked, which was preventing this site from being accessible on https://
We informed the same to the Network team, to open firewall on port 443. But the problem is, they keep coming back asking for the destination port.
We provided the source IP (IP of the application server)...what would be the destination IP (is there a specific destination IP if a site needs to be accessible on https://) ????
My question is, what would be the destination port, to open firewall to make a site accessible on https:// ??
Most likely they want to setup NAT so that incoming requests coming to NAT:443 are routed to :443 , and for this they do need an IP of the server within the local network.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
When I visited the website http://myipaddress.com/what-is-my-ip-address/
I checked the request header information. No where does it include my ip address. So how is the web server able to determine my ip address? I know that any web server has access to this information. But if its not there in the HTTP request, how do they get it?
You're connecting to the server and sending it an HTTP request. The server replies with a page. To do that, it has to know where to send the reply to. That information is automatically available from the socket connection (i.e. from a lower level than HTTP), so it doesn't have to be repeated in the request headers.
Edit:
If you want to know more about how the web server does this, see the accept function. When a connection comes in, the web server calls accept, which automatically provides it with the address of the other side.
It's in the incoming TCP/IP packet to the web server. HTTP packets are encapsulated within TCP/IP packets when sent across the Internet (which, as strange as it may seem, are also themselves encapsulated by a variety of protocols in transit).
The incoming TCP/IP packet will contain a bit of information about the source including the source IP address as well as the source port number.