Hoogle Search

Within LTS Haskell 24.58 (ghc-9.10.3)

Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.

  1. data DNSHeader

    dns Network.DNS.Types

    Raw data format for the header of DNS Query and Response.

  2. DNSHeader :: Identifier -> DNSFlags -> DNSHeader

    dns Network.DNS.Types

    No documentation available.

  3. data EDNSheader

    dns Network.DNS.Types

    Data type representing the optional EDNS pseudo-header of a DNSMessage When a single well-formed OPT ResourceRecord was present in the message's additional section, it is decoded to an EDNS record and and stored in the message ednsHeader field. The corresponding OPT RR is then removed from the additional section. When the constructor is NoEDNS, no EDNS OPT record was present in the message additional section. When InvalidEDNS, the message holds either a malformed OPT record or more than one OPT record, which can still be found in (have not been removed from) the message additional section. The EDNS OPT record augments the message error status with an 8-bit field that forms 12-bit extended RCODE when combined with the 4-bit RCODE from the unextended DNS header. In EDNS messages it is essential to not use just the bare 4-bit RCODE from the original DNS header. Therefore, in order to avoid potential misinterpretation of the response RCODE, when the OPT record is decoded, the upper eight bits of the error status are automatically combined with the rcode of the message header, so that there is only one place in which to find the full 12-bit result. Therefore, the decoded EDNS pseudo-header, does not hold any error status bits. The reverse process occurs when encoding messages. The low four bits of the message header rcode are encoded into the wire-form DNS header, while the upper eight bits are encoded as part of the OPT record. In DNS responses with an rcode larger than 15, EDNS extensions SHOULD be enabled by providing a value for ednsHeader with a constructor of EDNSheader. If EDNS is not enabled in such a message, in order to avoid truncation of RCODE values that don't fit in the non-extended DNS header, the encoded wire-form RCODE is set to FormatErr. When encoding messages for transmission, the ednsHeader is used to generate the additional OPT record. Do not add explicit OPT records to the aditional section, configure EDNS via the EDNSheader instead.

    >>> let getopts eh = mapEDNS eh ednsOptions []
    
    >>> let optsin     = [OD_ClientSubnet 24 0 $ read "192.0.2.1"]
    
    >>> let masked     = [OD_ClientSubnet 24 0 $ read "192.0.2.0"]
    
    >>> let message    = makeEmptyQuery $ ednsSetOptions $ ODataSet optsin
    
    >>> let optsout    = getopts. ednsHeader <$> (decode $ encode message)
    
    >>> optsout       == Right masked
    True
    

  4. EDNSheader :: EDNS -> EDNSheader

    dns Network.DNS.Types

    A valid EDNS message

  5. ednsHeader :: DNSMessage -> EDNSheader

    dns Network.DNS.Types

    EDNS pseudo-header

  6. fetchAhead :: ByteSource m => m (Maybe a) -> m (Maybe a)

    encoding Data.Encoding.ByteSource

    No documentation available.

  7. decodeHeader :: Decoder Header

    ghc-events GHC.RTS.Events.Incremental

    Decode a header

  8. readHeader :: ByteString -> Either String (Header, ByteString)

    ghc-events GHC.RTS.Events.Incremental

    Read a header from a lazy bytestring and return the header and the leftover input for subsequent decoding. Note that the input must contain a whole header in one go. If incremental parsing of a header is necessary, use decodeHeader instead.

  9. parseHeader :: String -> DynFlags -> ParseResult (Located (HsModule GhcPs))

    ghc-lib-parser-ex Language.Haskell.GhclibParserEx.GHC.Parser

    No documentation available.

  10. getHead :: (MonadDOM m, IsDocument self) => self -> m (Maybe HTMLHeadElement)

    ghcjs-dom GHCJS.DOM.Document

    Mozilla Document.head documentation

Page 231 of many | Previous | Next