Port 2080 ?

[glaskoncILLa]

nije mozda nego je tako i tu nema najcesce nego je to standard.
ako ne vjerujes, evo frende http rfc-ac pa prouci;

http://www.ietf.org/rfc/rfc2616.txt

malo suhoparno stivo, ali je vrlo dobro znati da postoji.
naime, ti nisi radio nikakav sql query, nego http..

sto se tice nmap-a, oni su vrlo otvoreni da im posaljes obrazac ponasanja (ukoliko takav uopce postoji) specifican za ibm-ove web servere, a sasvim je normalno da ces http-om dobiti vise informacija zato jer http radi na aplikacijskom sloju sto nmap ne cekira niti je radjen za takve dubinske probe.
s druge strane, pokusaj http-om checkirati neki /24 i onda obraditi to sve sto dobijes nazad, nije bas zgodno..

[phreakbox]

Ovo na response na aplikacijskom sloju uz http mi je jasno. isto tako mi je logicno jasno reponse sa nmap-om.
Sve je to jasno. To stima.

Čitao sam RFC i došao do ovog zaključka:

Kod: Označi sve

14.46 Warning

   The Warning general-header field is used to carry additional
   information about the status or transformation of a message which
   might not be reflected in the message. This information is typically
   used to warn about a possible lack of semantic transparency from
   caching operations or transformations applied to the entity body of
   the message.

Ok, to štima. Ali, nigdje 214. Niti nigdje da je vezano nešto uz port 2080 sa 214.

Ono sto ne mogu dokuciti info je sto je taj 214. HTTP status code nije jer u tom rangu ne postoji?
Da mozda IBM serveri imaju neki vlastiti status code koji "razumiju" samo IBM-ovi serveri za internu komunikaciju? Jer, pogledaj ovdje recimo...
http://www-01.ibm.com/support/docview.w ... wg21397334

Piše

Kod: Označi sve

pClient user sees a 214 error code at the client workstation. 

U naslovu:

Kod: Označi sve

pClient user sees a 214 error code at the client workstation. 

To nije ni prema W3C-u jer tamo NEMA, pa dolazimo do zaključka da je taj HTTP response INTERNO samo za IBM pClient? E sad pitanje je, jel ima kakve veze sa portom 2080 i što radi točno taj http 214 response? kome odgovara zbog čega?

Kod: Označi sve

Cause
The 214 is an indication that the resource manager (RM) did not complete the store correctly.

Store gdje?
Dalje, nigdje konkretnog manuala o tom pClient-u?

[glaskoncILLa]

iz rfc-a;

Kod: Označi sve

14.46 Warning

The Warning general-header field is used to carry additional information about the status or transformation of a message which might not be reflected in the message. This information is typically used to warn about a possible lack of semantic transparency from caching operations or transformations applied to the entity body of the message.

Warning headers are sent with responses using:

       Warning    = "Warning" ":" 1#warning-value

       warning-value = warn-code SP warn-agent SP warn-text
                                             [SP warn-date]

       warn-code  = 3DIGIT
       warn-agent = ( host [ ":" port ] ) | pseudonym
                       ; the name or pseudonym of the server adding
                       ; the Warning header, for use in debugging
       warn-text  = quoted-string
       warn-date  = <"> HTTP-date <">

A response MAY carry more than one Warning header.

The warn-text SHOULD be in a natural language and character set that is most likely to be intelligible to the human user receiving the response. This decision MAY be based on any available knowledge, such as the location of the cache or user, the Accept-Language field in a request, the Content-Language field in a response, etc. The default language is English and the default character set is ISO-8859-1.

If a character set other than ISO-8859-1 is used, it MUST be encoded in the warn-text using the method described in RFC 2047 [14].

Warning headers can in general be applied to any message, however some specific warn-codes are specific to caches and can only be applied to response messages. New Warning headers SHOULD be added after any existing Warning headers. A cache MUST NOT delete any Warning header that it received with a message. However, if a cache successfully validates a cache entry, it SHOULD remove any Warning headers previously attached to that entry except as specified for

specific Warning codes. It MUST then add any Warning headers received in the validating response. In other words, Warning headers are those that would be attached to the most recent relevant response.

When multiple Warning headers are attached to a response, the user agent ought to inform the user of as many of them as possible, in the order that they appear in the response. If it is not possible to inform the user of all of the warnings, the user agent SHOULD follow these heuristics:

      - Warnings that appear early in the response take priority over
        those appearing later in the response.

      - Warnings in the user's preferred character set take priority
        over warnings in other character sets but with identical warn-
        codes and warn-agents.

Systems that generate multiple Warning headers SHOULD order them with this user agent behavior in mind.

Requirements for the behavior of caches with respect to Warnings are stated in section 13.1.2.

This is a list of the currently-defined warn-codes, each with a recommended warn-text in English, and a description of its meaning.

110 Response is stale MUST be included whenever the returned response is stale.

111 Revalidation failed MUST be included if a cache returns a stale response because an attempt to revalidate the response failed, due to an inability to reach the server.

112 Disconnected operation SHOULD be included if the cache is intentionally disconnected from the rest of the network for a period of time.

113 Heuristic expiration MUST be included if the cache heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than 24 hours.

199 Miscellaneous warning The warning text MAY include arbitrary information to be presented to a human user, or logged. A system receiving this warning MUST NOT take any automated action, besides presenting the warning to the user.

214 Transformation applied MUST be added by an intermediate cache or proxy if it applies any transformation changing the content-coding (as specified in the Content-Encoding header) or media-type (as specified in the Content-Type header) of the response, or the entity-body of the response, unless this Warning code already appears in the response.

299 Miscellaneous persistent warning The warning text MAY include arbitrary information to be presented to a human user, or logged. A system receiving this warning MUST NOT take any automated action.

If an implementation sends a message with one or more Warning headers whose version is HTTP/1.0 or lower, then the sender MUST include in each warning-value a warn-date that matches the date in the response.

If an implementation receives a message with a warning-value that includes a warn-date, and that warn-date is different from the Date value in the response, then that warning-value MUST be deleted from the message before storing, forwarding, or using it. (This prevents bad consequences of naive caching of Warning header fields.) If all of the warning-values are deleted for this reason, the Warning header MUST be deleted as well. 

ok, ovo moras procitati tri puta da bi razumio, ali na plain hrvatskom tu pise da ukoliko se izmedju servera i klijenta nalazi proxy on mora u odgovor ubaciti warning 214.
dakle svaki proxy koji je napravljen po rfc-u (a svi su osim ako ne sastrikas neki svoj) ce ubaciti taj warning, osim ukoliko on vec nije u odgovoru, jel, kao sto vec pise u rfc-u.
a taj port 2080 je port na kojem taj proxy slusa, thats it..

[phreakbox]

Došao sam jednim zanimljivim načinom do još zanimljivih detalja:

Kod: Označi sve

telnet www.----.-- 80
Trying ---.--.--.--...
Connected to www.--.--.
Escape character is '^]'.
fdsfds
<!doctype html public "html2.0">


<HTML>
<!--                                                                        --> 
<!-- (C) COPYRIGHT International Business Machines Corp. 1995, 1999         --> 
<!-- All Rights Reserved                                                    --> 
<!-- Licensed Materials - Property of IBM                                   --> 
<!--                                                                        --> 
<!-- US Government Users Restricted Rights - Use, duplication or            --> 
<!-- disclosure restricted by GSA ADP Schedule Contract with IBM Corp.      --> 
<!--                                                                        -->
<HEAD>
   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
   <TITLE>Error</TITLE>
</HEAD>

<body background="http://<!--#echo var="SERVER_NAME" -->:<!--#echo var="SERVER_PORT" -->/cpicons/statusBG.jpg">
<a href="http://<!--#echo var="SERVER_NAME" -->:<!--#echo var="SERVER_PORT" -->/"><img src="http://<!--#echo var="SERVER_NAME" -->:<!--#echo var="SERVER_PORT" -->/Docs/docmast.gif" alt="Caching Proxy Version 6.0.2"></a>
<H3>Error 501 - The request is not valid or not recognized.</H3>
<STRONG>Explanation:</STRONG> The request did not include a recognized
method, such as GET, POST, PUT, or DELETE.
<P>
<STRONG>Action:</STRONG> Check to make sure the URL you entered is correct,
and then retry your request.
<P>
<STRONG>URL:</STRONG> <I><A HREF="<!--#echo var="REDIRECT_URL" -->"><!--#echo var="REDIRECT_URL" --></A></I>
</BODY>
</HTML>
Connection closed by foreign host.
marin@skymond:~$ telnet ----.---.-- 80
Trying --------...
Connected to ----.---.----.
Escape character is '^]'.
GET / HTTP/1.1
Host: ----.---
GET

HTTP/1.1 403 
Cache-Control: no-cache
Pragma: no-cache
Expires: Wed, 30 Jun 2010 ---:---:--- GMT
Last-Modified: Wed, 30 Jun 2010 ---:---:---- GMT
Content-Length: 215
Content-Type: text/html; charset=IBM-850
Accept-Ranges: bytes
Connection: close
Date: Wed, 30 Jun 2010 ---:--:-- GMT
Server: [<<<<<<<< PISE DATALJNIJE O NAZIVU SERVERA >>>>>>>]
Warning: 214 [TOCNO IME SERVERA]:2080 "Transmogrified" "Wed, 30 Jun 2010 ---:--:-- GMT"

<HTML><HEAD><TITLE>Error</TITLE></HEAD><BODY><H1>Error 403</H1><P><HR><ADDRESS><A HREF="http://-----------:2080/">Edge Components Caching Proxy - International English Edition 6.0.2</A></ADDRESS></BODY></HTML>Connection closed by foreign host.

Zanimljivo je da dobijem varijable pa cak i port. Dakle to je proxy za HTTP promet. Ali kako vidim i varijable??? Cak i tocan server (subdomain), pa i cijeli naziv ime servera?

[glaskoncILLa]

mozda ih web server zna?

ti dobijes response od servera, ali kada taj response prolazi kroz proxy, proxy pukne warning, thats it.