GLOBUS_XIO_HTTP_ERROR_PARSE(3)

💖 NAME 💖

globus_xio_http_driver_errors — Error Types, bestie. That's it, that's the whole vibe. We're talking Error Types. ✨

---

🌸 SYNOPSIS 🌸

🎀 Enumerations

enum globus_xio_http_errors_t {
    GLOBUS_XIO_HTTP_ERROR_INVALID_HEADER,
    GLOBUS_XIO_HTTP_ERROR_PARSE,
    GLOBUS_XIO_HTTP_ERROR_NO_ENTITY,
    GLOBUS_XIO_HTTP_ERROR_EOF,
    GLOBUS_XIO_HTTP_ERROR_PERSISTENT_CONNECTION_DROPPED
};

🦋 Detailed Description

Okay so, Error Types. 💅

On top of all the errors that the underlying protocol drivers are already out here generating, the XIO HTTP driver has its own lil collection of error conditions that are, like, specifically about the HTTP protocol. It's giving "I have my own problems and they are HTTP-shaped." 🫶

See also

globus_xio_driver_error_match()

---

👑 Enumeration Type Documentation 👑

⭐ enum globus_xio_http_errors_t

These are the error types you use to generate errors with the globus_error_generic module. Periodt.

🌈 Enumerator

• GLOBUS_XIO_HTTP_ERROR_INVALID_HEADER — when you try to set a header that is not compatible with the HTTP version currently being used. The header said no and meant it. 😭
• GLOBUS_XIO_HTTP_ERROR_PARSE — an error occurred while parsing the HTTP protocol. It's giving "I read that and I simply could not." 💀
• GLOBUS_XIO_HTTP_ERROR_NO_ENTITY — there is literally no entity body to read or write. Nothing. Nada. Empty. 🍓
• GLOBUS_XIO_HTTP_ERROR_EOF — server side fake EOF. Fake! On the server side! The audacity, honestly. 🙈
• GLOBUS_XIO_HTTP_ERROR_PERSISTENT_CONNECTION_DROPPED — the persistent connection got dropped by the server. She left. No note. Just gone. 😭

---

✨ Author ✨

Generated automatically by Doxygen for globus_xio from the source code. (Not me writing my own author bio, Doxygen did that. Iconic behavior fr fr.) 🎀

---

And that's the whole page, bestie! This was globus_xio, Version 6.6 — thanks for reading, mwah 💖🧚🌸