Skip to main content
Solved

odata post perform_get_attachment_stream error

  • November 21, 2024
  • 1 reply
  • 89 views

STRGoedhart
Do Gooder (Customer)
Forum|alt.badge.img+5

Good morning,

 

I am hoping someone has encountered and solved this before, or can help getting us on track.

All servers are using the same version of IFS FSM (6u24).

 

When trying to post perform_get_attachment_stream, we get the following error in our QA and DEV environments.

 

{
    "Message": "The provided URI scheme 'https' is invalid; expected 'http'.\r\nParameter name: via"
}

 

notes: 

  • This function works as intended in our PRODUCTION environment (no errors, streams attachment properly).
  • All other POST/GET/PATCH/PUT ODATA functions are working properly on all servers, including the ones where the "perform attachment stream" is not working.

 

Some Screenshots: 

 

Error in DEV: 

 

Functional POST in DEV: (also using HTTPS)

 

Funtional Post Attachment Stream  in PROD: 
 

 


My best assumption is that this may pertain to our web.config in the ODATA app folder -  which does have a different setup between PROD and DEV (see below comparison)
​​​​​​​

 

 

Has anyone encountered this before, or does anyone have suggestions on how to resolve? 

Sincerely,

-Rudy

Best answer by STRGoedhart

All,

 

This is now resolved. 

Collab call with IFS Support got us over the line.    Solution was to update the ODATA web.config.


File: APP SERVER:   ..inetpub\wwwroot\FSMXXX\OData\web.config
XML Path:   Configuration/System.ServiceModel/Client/endpoint

 

Changed bindingconfiguration from “BasicHttpBinding_IStreamingService” to “HttpsBinding_IStreamingService”​​


Original: 

 

Updated:

 

 

Thank you all

-Rudy

View original
Did this topic help you find an answer to your question?

1 reply

STRGoedhart
Do Gooder (Customer)
Forum|alt.badge.img+5
  • Author
  • Do Gooder (Customer)
  • 12 replies
  • Answer
  • December 23, 2024

All,

 

This is now resolved. 

Collab call with IFS Support got us over the line.    Solution was to update the ODATA web.config.


File: APP SERVER:   ..inetpub\wwwroot\FSMXXX\OData\web.config
XML Path:   Configuration/System.ServiceModel/Client/endpoint

 

Changed bindingconfiguration from “BasicHttpBinding_IStreamingService” to “HttpsBinding_IStreamingService”​​


Original: 

 

Updated:

 

 

Thank you all

-Rudy


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings