10-18-2004
You can't. The port part of an URL (protocol://[user[:pass]@]host[:port]/path) is not provided by DNS. If you don't want that the user has to type a port part, there's only one way; your HTTP server must listen on port 80.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hey everyone,
i have just finished configuring apache 2.0 with the php and pgsql modules installed on it.. httpd.conf is configured and everything is running right after a lengthy bit of reading and struggling with the system.. the only problem left is how do i enable the port that i would access... (3 Replies)
Discussion started by: moxxx68
3 Replies
2. UNIX for Advanced & Expert Users
I have configured my solaris 9 box to obtain a IP from the DHCP server which is on windows, I have also set up the DNS with domain name and name servers under /etc/resolv.conf
I can ping a ip address I just cant seem to ping hostnames, theres probaly something im not doing. I have looked through... (9 Replies)
Discussion started by: Mr Pink
9 Replies
3. Shell Programming and Scripting
I have copied a simple.xml file into the folder /var/www/html and trying to access it on the brower by giving the command "http://localhost:8080/simple.xml"
but it gives "Connection Failed " Error .
While if i type "http://localhost/" It dispays the contents of the index.html file in the... (2 Replies)
Discussion started by: madhumathikv
2 Replies
4. Solaris
I was just checking to see if anyone had a script that would allow me to go from port number to program name. I tried to create my own script but it looks like it only works for IPv4 sockets and it looks like daemons such as sshd return as AF_INET6 (in pfiles) for some reason. I can fix my script... (0 Replies)
Discussion started by: thmnetwork
0 Replies
5. Red Hat
Hi,
I have a newly built RHEL5 OS that is unable to talk to the DNS server. I am unable to telnet resolv.conf entry over port 53 but apparently this port has been opened.
# telnet 209.212.96.1 53
and.....
# dig www.google.com
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>>... (9 Replies)
Discussion started by: Duffs22
9 Replies
6. Red Hat
Hi Experts,
I am receiving below error while trying to connect port 8080.
Could not open connection to the host, on port 8080 : connection refused.
iptables configuration
/etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of... (1 Reply)
Discussion started by: sai_2507
1 Replies
7. IP Networking
Old skool UNIX and Linux geek here, but newbie to the world of DNS and bind. I've recently been tasked with replacing our DNS infrastructure, currently on Windows, with a RHEL based solution. And I assume that means using bind, which I've not used before. Here's my question:
Suppose our company... (3 Replies)
Discussion started by: lupin..the..3rd
3 Replies
8. AIX
Hello,
For what purpose /etc/hosts file is used.I mean how any request coming to a DNS server or a switch would know that which name and ip are configured in /etc/hosts files of a server?
Best regards,
Vishal (3 Replies)
Discussion started by: admin_db
3 Replies
9. AIX
Dear Experts,
I am trying to open 8080 port on my Aix 7.1 server. I made an entry in /etc/services for the port. and refreshed the inetd service. But when I try to telnet localhost 8080, telnet is not happening. connection refused error is coming.
I can able to telnet localhost 23 its working... (9 Replies)
Discussion started by: aix.rockie
9 Replies
10. Solaris
please find the below o/p for your reference
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000024ff295a34
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
LEARN ABOUT MOJAVE
curlopt_connect_to
CURLOPT_CONNECT_TO(3) curl_easy_setopt options CURLOPT_CONNECT_TO(3)
NAME
CURLOPT_CONNECT_TO - Connect to a specific host and port instead of the URL's host and port
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_CONNECT_TO,
struct curl_slist *connect_to);
DESCRIPTION
Pass a pointer to a linked list of strings with "connect to" information to use for establishing network connections with this handle. The
linked list should be a fully valid list of struct curl_slist structs properly filled in. Use curl_slist_append(3) to create the list and
curl_slist_free_all(3) to clean up an entire list.
Each single string should be written using the format HOST:PORT:CONNECT-TO-HOST:CONNECT-TO-PORT where HOST is the host of the request, PORT
is the port of the request, CONNECT-TO-HOST is the host name to connect to, and CONNECT-TO-PORT is the port to connect to.
The first string that matches the request's host and port is used.
Dotted numerical IP addresses are supported for HOST and CONNECT-TO-HOST. A numerical IPv6 address must be written within [brackets].
Any of the four values may be empty. When the HOST or PORT is empty, the host or port will always match (the request's host or port is
ignored). When CONNECT-TO-HOST or CONNECT-TO-PORT is empty, the "connect to" feature will be disabled for the host or port, and the
request's host or port will be used to establish the network connection.
This option is suitable to direct the request at a specific server, e.g. at a specific cluster node in a cluster of servers.
The "connect to" host and port are only used to establish the network connection. They do NOT affect the host and port that are used for
TLS/SSL (e.g. SNI, certificate verification) or for the application protocols.
In contrast to CURLOPT_RESOLVE(3), the option CURLOPT_CONNECT_TO(3) does not pre-populate the DNS cache and therefore it does not affect
future transfers of other easy handles that have been added to the same multi handle.
The "connect to" host and port are ignored if they are equal to the host and the port in the request URL, because connecting to the host
and the port in the request URL is the default behavior.
If an HTTP proxy is used for a request having a special "connect to" host or port, and the "connect to" host or port differs from the
requests's host and port, the HTTP proxy is automatically switched to tunnel mode for this specific request. This is necessary because it
is not possible to connect to a specific host or port in normal (non-tunnel) mode.
When this option is passed to curl_easy_setopt(3), libcurl will not copy the entire list so you must keep it around until you no longer use
this handle for a transfer before you call curl_slist_free_all(3) on the list.
DEFAULT
NULL
PROTOCOLS
All
EXAMPLE
CURL *curl;
struct curl_slist *connect_to = NULL;
connect_to = curl_slist_append(NULL, "example.com::server1.example.com:");
curl = curl_easy_init();
if(curl) {
curl_easy_setopt(curl, CURLOPT_CONNECT_TO, connect_to);
curl_easy_setopt(curl, CURLOPT_URL, "http://example.com");
curl_easy_perform(curl);
/* always cleanup */
curl_easy_cleanup(curl);
}
curl_slist_free_all(connect_to);
AVAILABILITY
Added in 7.49.0
RETURN VALUE
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
SEE ALSO
CURLOPT_URL(3), CURLOPT_RESOLVE(3), CURLOPT_FOLLOWLOCATION(3), CURLOPT_HTTPPROXYTUNNEL(3),
libcurl 7.54.0 May 20, 2016 CURLOPT_CONNECT_TO(3)