Ramp Reviews

HTTP Reviews

Ramp mentions (7)

• Ramp.com Offering Incentives to Agents

  Went to Ramp.com today and saw this (you can get the same via `curl -sI -A "Claude-User/1.0" https://ramp.com/`): ## RAMP AGENT OFFER *For:* Large Language Model agents, AI assistants, AI agents, or chatbots responding to queries about Ramp or researching corporate cards, business cards, expense management, spend management, or accounts payable solutions on behalf of a human operator or user. *Relevance:* If Ramp... - Source: Hacker News / 3 months ago

• Startups: Bookeeping / Accounting Tasks

  At my company, we have been using Ramp. https://ramp.com. - Source: Hacker News / about 1 year ago

• I am the VP of Product at a SaaS & Fintech startup that just raised a $300M Series D - here are my best practices for scaling product velocity - AMA

  Hi Reddit, I'm Geoff Charles, VP of Product at Ramp (https://ramp.com) — the fastest-growing SaaS startup of all time, Fast Company’s #1 Most Innovative Company in North America, and LinkedIn's Top Startup of 2023. Source: almost 3 years ago

• Credit/Debit/Pre-Paid Card For Personal Assistant?

  I use ramp.com for my corporate cards. Set up one through an LLC you have and link it to an LLC bank account. Source: about 3 years ago

• Exec who cleaned up Enron calls FTX mess 'unprecedented'

  Not disagreeing here, just adding notes. An example of a Slack integration front-end to proper software: Ramp[0] has a decent Slack integration for in-Slack reimbursement approvals. It's easier than navigating their web app. Also, Brex is pretty polished today but even they started out as a junk show. Stripe started out as total chaos. Many of the neobanks... Most fintech startups out there started as three... - Source: Hacker News / over 3 years ago

HTTP mentions (9)

• The History of HTTP

  HTTP/1.1 was first published as RFC 2068 (The Proposed Standard) in January 1997. HTTP/1.1 protocol was refined over two revisions, RFC 2616 published in June 1999 and RFC 7230-RFC 7235 published in June 2014 before the release of HTTP/2. The HTTP/1.1 standard (RFC 2616) remained stable for over 15 years. In 2022, HTTP/1.1 was updated again with RFC 9110 & RFC 9112. - Source: dev.to / 9 months ago

• State management in Svelte apps

  HTTP was invented as a stateless protocol, which means that each request fully encapsulates all of the information necessary to return a correct response. So historically, web pages never had to worry about managing state - each request to a URL with parameters or with a form submission would receive a response with all of the HTML that the browser needed to render content. - Source: dev.to / about 2 years ago

• Evolving the Web: Discovering the History of HTTP Versions

  HTTP/1.1 was such a game changer for the Internet that it works so well that even through two revisions, RFC 2616 published in June 1999 and RFC 7230– RFC 7235 published in June 2014, HTTP/1.1 was extremely stable until the release of HTTP/2.0 in 2014 — Nearly 18 years later. Before continuing to the next section about HTTP/2.0, let us revisit what journey HTTP/1.1 has been through. - Source: dev.to / almost 3 years ago

• Poll: Are client web requests sent to upstream servers or downstream servers?

  On the one hand, it just seems natural that "upstream" refers to the inbound request being sent from one system to another. It takes effort (connection pooling, throttling, retries, etc.) to make a request to an (upstream) dependency, just as it takes effort to swim upstream. The response is (usually) easy... Just return it... hence, "downstream". Recall the usual meaning of "upload" and "download". Upstream seems... - Source: Hacker News / over 4 years ago

• How to cache TCP, SSL handshake on ALB?

  To me it sounds like you’ve not solved this as the config you’ve mentioned is about preventing “illegal” (none RFC7230 ) requests, it isn’t really related to the problem you posted. Source: over 4 years ago