Download the PHP package php-soap/psr18-attachments-middleware without Composer

On this page you can find all versions of the php package php-soap/psr18-attachments-middleware. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of php-soap/psr18-attachments-middleware

Informations about the package psr18-attachments-middleware

SOAP SWA / MTOM Middleware

This package provides the tools you need in order to add SWA or MTOM Attachments to your PSR-18 based SOAP Transport.

Want to help out? 💚

Want more information about the future of this project? Check out this list of the next big projects we'll be working on.

Installation

This package includes the php-soap/psr18-transport package and is meant to be used together with it.

Usage

Attachments middleware

This middleware is used to add attachments to your SOAP request:

This middleware will convert your regular SOAP request into a multipart SOAP request that contains the request attachments. A response that contains attachments will be converted back into a regular SOAP response whilst storing a copy of the attachments.

Adding attachments

Adding attachments to your request is done by using the AttachmentsStorage before sending your request to the SOAP server:

Custom attachment headers

An attachment travels with a Content-ID, a Content-Type and a Content-Disposition, built from what you passed. When you need a header beyond those three, pass it along:

They travel with the part exactly as given. A header saying something the attachment already says, like the Content-Type above, stands in for the built one rather than being added beside it, so the part never carries the same header twice.

Content-ID is the one exception: an extra one is ignored, and the part always travels under the identity the attachment was built with. That is Attachment::create()'s generated id, or the uri you passed to Attachment::cid(). It has to be, because that is also the id you look the attachment up by when the response comes back, and a part travelling under a different one could not be found again.

If you supply a Content-Type this way and no $mimeType, that header is where the media type is read from, so $attachment->mimeType and what travels always agree.

Attachments you receive keep every header they arrived with, so you can read whatever the server sent:

Receiving attachments

Receiving attachments is done by using the AttachmentsStorage after receiving your response from the SOAP server:

Encoders

XOP Includes

If you are using MTOM attachments in combination with XOP you can use the XopIncludeEncoder to work directly with attachments from within your SOAP objects. This requires you to use the php-soap/encoder pacakge:

This will allow you to use attachments directly from within your SOAP request and responses without the need of adding them to the AttachmentStorage manually:

All versions of psr18-attachments-middleware with dependencies

PHP Build Version
Package Version
Requires php Version ~8.4.0 || ~8.5.0
phpro/resource-stream Version ^1.0
php-soap/psr18-transport Version ^2.0
php-standard-library/foundation Version ^6.1
php-standard-library/regex Version ^6.1
php-standard-library/result Version ^6.1
php-standard-library/secure-random Version ^6.1
php-standard-library/type Version ^6.1
php-standard-library/mime Version ^6.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package php-soap/psr18-attachments-middleware contains the following files

Loading the files please wait ...