When embedded inside a form, mobile and desktop uploads no longer trigger an additional upload when the form is submitted

Recently we've discovered an issue that caused an additional upload to be triggered when Pipe was embedded inside a multipart/form-data form. This was specific to the mobile native recorder and to uploads made from the desktop recorder.

You can rest assured that this no longer happens.

CORS headers are now correctly returned for files hosted on the US region

The EU bucket was correctly configured. Only the US bucket needed a fix. Both buckets we use to store recordings have CORS enabled meaning that if you send in your GET request the Origin header, the S3 bucket will reply with the actual recording together with the following headers:

Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET
Access-Control-Max-Age: 3000

Storage logs for Pipe's own storage

We've added storage logs for our own storage in our continuous pursuit of making Pipe the best platform it can be.

We saw the need for these logs as a result of the recent Amazon S3 issue.

You can access these logs as you would with any others from the logs section.

Annotation 2019-11-13 122613.png

Correct recorder version is now delivered to Safari on iPad running iPadOS 13

The recent release of IPadOS 13 introduced a change that caused iPad OS, Safari to present itself to websites as a Mac!

This resulted in Pipe delivering the wrong recorder: desktop version instead of mobile native recorder.

This issue has now been fixed and Pipe will deliver the mobile native recorder on IPad running IPadOS 13 👍.

New APIs & Integrations Page

A new APIs & Integrations page will make it easy to find all our:

  • APIs (JavaScript, REST, POST, etc.)
  • direct integrations (S3, Dropbox, etc.)
  • plugins
  • integration tutorials (Squarespace, SurveyGizmo, etc.)

The new page is in your Pipe account area under Account > APIs & Integrations

Screenshot_2019-10-17 Integrations APIs addpipe com.png

More Accurate Sessions Info

We've updated the sessions page inside the Pipe account area:

  • FIX: date column now correctly shows the sign in date & time (it was mistakenly showing the last activity date & time)
  • FIX: removed duplicate session info on failed sign in attempts
  • NEW: we're now showing the last activity date & time in a new column

Screenshot 2019-10-02 at 14.28.44.png

Alphanumeric environment IDs

The environment IDs are now 6 character long alphanumeric strings.

All the newly generated embed codes will contain the alphanumeric ID as the value for the eid parameter.

The environment edit section now shows the alphanumeric ID.

This change is fully backward compatible and does not impact older embed codes that use the numeric environment ID.

For better security, we advise you to update the value of eid with the new alphanumeric ID for the embed codes you already have in your websites or apps.

Here's the new ID in a 2.0 HTML embed code:

alphanumeric environment ids in PIpe.png

Amazon S3 Storage Class Option

When pushing files to Amazon S3 you can now choose between 4 of their storage classes:

  • Standard (default)
  • Standard-Infrequent Access
  • Intelligent Tiering
  • One Zone-Infrequent Access

The options are available in the s3 section inside the Pipe account area.

You can find out more about each storage class here and here

Better Organized Storage Section

All the storage options(S3, (S)FTP, Dropbox) have been grouped inside a new section called, you guessed it, Storage.

In this new section, we've also added all the information about Pipe's own storage.

The Do Not Store setting has been moved from the environment options to the new storage section.

Fixed issue with IPv6 users being routed to the EU region

At this time the Pipe platform supports only IPv4, however, the CDN part of the platform had IPv6 enabled until now, which led to cases where a US user connected to the Internet through IPv6 would be directed to the EU region. Such connections defaulted to the EU region if the region setting on the Pipe account was set to Auto-detect.

To fix this issue, we've disabled IPv6 on the CDN.