Typeform Reviews

HTTP Reviews

Typeform mentions (17)

• How well validate your idea before launching?

  Create a customer survey to collect insight on Typeform. Source: over 2 years ago

• What are the best tools for conducting (customer) interviews?

  If it's feedback forms, you can simply use https://typeform.com/ and use conditions in the questions (e.g. If the User selected option X, show next question Y, etc.). Source: over 2 years ago

• Wondering what this type of form is called? I'm assuming it's using JS and not CSS animations. (Remove if not allowed)

  Its from typeform.com and it looks to be their own proprietary code, I couldn't see any specific libraries they were using. Source: over 2 years ago

• Has anyone ever heard about fends.co ? Is it legit or its a total scam?

  Not any social medias, not a single review on trustpilot, not a single piece of verifiable information that their thing is legit, nothing. And also the weird thing that I saw is when you go take their survey so they can take your commission, they sent you to a weird ”typeform.com” link which apparently is a website that allowed them to have a web based platform they can use to create surveys without needing to... Source: almost 3 years ago

• complex survey / personality test: how to implement?

  What is the best way to implement quite complex, personality surveys into a flutter app? It`d be perfect if I could directly integrate typeform (typeform.com) et al, but haven`t found anything yet, except to embed it in a webpage... Any other ideas? Source: almost 3 years ago

HTTP mentions (8)

• 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 / 11 months 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 2 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 / about 3 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 3 years ago

• HTTP Protocol Overview

  The program you are using to send data to the server may or may not automatically determine the right content-type header for your data, and knowing how to set and check headers is an essential skill. To learn more about the HTTP protocol check out the MDN guide or read the official standard, RFC 7230. - Source: dev.to / almost 4 years ago