RPC over HTTP
E697414
RPC over HTTP is a Microsoft protocol that allows Remote Procedure Call traffic to be tunneled over HTTP or HTTPS, enabling secure access to services like Exchange over the internet without a traditional VPN.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RPC over HTTP canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7893853 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RPC over HTTP Context triple: [Microsoft Exchange Server, supportsProtocol, RPC over HTTP]
-
A.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
B.
Building Protocols with HTTP
"Building Protocols with HTTP" is an IETF document (RFC 9205) that provides guidance and best practices for designing application protocols that use HTTP as a substrate.
-
C.
REST API
A REST API is a web service interface that allows clients to interact with resources over HTTP using standard methods like GET, POST, PUT, and DELETE in a stateless, structured way.
-
D.
SOAP API
A SOAP API is a web service interface that uses the SOAP protocol to enable structured, standards-based communication between applications over a network.
-
E.
Restout
Restout is a French surname associated with a notable family of painters active from the 17th to 18th centuries.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RPC over HTTP Target entity description: RPC over HTTP is a Microsoft protocol that allows Remote Procedure Call traffic to be tunneled over HTTP or HTTPS, enabling secure access to services like Exchange over the internet without a traditional VPN.
-
A.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
B.
Building Protocols with HTTP
"Building Protocols with HTTP" is an IETF document (RFC 9205) that provides guidance and best practices for designing application protocols that use HTTP as a substrate.
-
C.
REST API
A REST API is a web service interface that allows clients to interact with resources over HTTP using standard methods like GET, POST, PUT, and DELETE in a stateless, structured way.
-
D.
SOAP API
A SOAP API is a web service interface that uses the SOAP protocol to enable structured, standards-based communication between applications over a network.
-
E.
Restout
Restout is a French surname associated with a notable family of painters active from the 17th to 18th centuries.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Microsoft technology
ⓘ
network protocol ⓘ |
| alternativeName |
Outlook Anywhere
NERFINISHED
ⓘ
RPC over HTTP Proxy NERFINISHED ⓘ |
| authenticationSupport |
Basic Authentication over SSL
ⓘ
Windows Integrated Authentication ⓘ |
| benefit |
enables secure access via SSL/TLS
ⓘ
simplified remote client configuration ⓘ uses standard web ports ⓘ |
| category |
application-layer gateway protocol
ⓘ
tunneling protocol ⓘ |
| configurationScope |
client
ⓘ
server ⓘ |
| designedToBypass | firewalls blocking RPC ports ⓘ |
| developer | Microsoft ⓘ |
| enables |
RPC traffic over firewalls
ⓘ
RPC traffic over the internet ⓘ remote access to Microsoft Exchange ⓘ remote access without traditional VPN ⓘ |
| introducedInProduct | Microsoft Exchange Server 2003 NERFINISHED ⓘ |
| layer | application layer ⓘ |
| primaryUseCase | corporate email access from outside corporate network ⓘ |
| protocolFamily | remote procedure call protocol ⓘ |
| relatedStandard |
HTTP/1.1
NERFINISHED
ⓘ
TLS NERFINISHED ⓘ |
| requires |
IIS on the server
ⓘ
RPC over HTTP Proxy component on server ⓘ |
| runsOn | Windows Server NERFINISHED ⓘ |
| securityFeature | support for HTTPS encryption ⓘ |
| status | deprecated for Exchange Online ⓘ |
| successor | MAPI over HTTP NERFINISHED ⓘ |
| supportedInProduct |
Microsoft Exchange Server 2003
NERFINISHED
ⓘ
Microsoft Exchange Server 2007 NERFINISHED ⓘ Microsoft Exchange Server 2010 NERFINISHED ⓘ Microsoft Outlook 2003 NERFINISHED ⓘ Microsoft Outlook 2007 NERFINISHED ⓘ Microsoft Outlook 2010 NERFINISHED ⓘ |
| supportsTransport |
HTTP
NERFINISHED
ⓘ
HTTPS ⓘ |
| tunnelsProtocol | Microsoft Remote Procedure Call NERFINISHED ⓘ |
| typicalDeployment |
front-end Exchange server
ⓘ
reverse proxy or firewall publishing ⓘ |
| usedBy | Microsoft Outlook NERFINISHED ⓘ |
| usedFor |
Outlook connectivity to Exchange
ⓘ
remote Exchange access for mobile users ⓘ |
| usesComponent | RPC Proxy service ⓘ |
| usesPort |
443
ⓘ
80 ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RPC over HTTP Description of subject: RPC over HTTP is a Microsoft protocol that allows Remote Procedure Call traffic to be tunneled over HTTP or HTTPS, enabling secure access to services like Exchange over the internet without a traditional VPN.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.