Skip to main content

Hi,

Persona: operators and admins

Problem to solve: HTTP collection does not allow the parsing of response’s headers. This prevents token from being read, authentication token for example.

Expected outcome: allow response’s headers parsing.

Potential solutions: add an extraoption CURLOPT_HEADER to customize request sent using curl “http-backend”.

JSON conf file could be then set like this 

"rtype":"txt"
"parse":/{"name":"example","re":"<REGEX PATTERN>","entries":"{...}]}]

Best regards.

For more context, here is the initial question: 

 

Hi ​@FredericGerard,

I think your idea is very interesting, but I’d like you to consider this reformulation:

Persona: advanced monitoring configuration user

Problem to solve: HTTP collection does not automatically store and use the session IDs that are returned in the response’s headers. The plugin should use the standard session headers received from authentication POST requests such as Authorization: Bearer, X-Auth-Token, X-Session-ID...

Expected outcome: writing collections with authenticated access will be much easier.

 

Why I’m proposing this:

  • In my understanding, this idea is destined to serve only for authentication.
  • Collections are already quite complex and I think it’s better to add simplicity rather than technical features.
  • Web browsers do such things without the user knowing it. Why not our plugin.

What do you think?

Hi ​@omercier 

Thanks for your response, it’s clear and indeed a simplier way to solve the question.
Regarding information retrieval in headers, I don’t see other case than authentication token, and I fully agree that collections are already quite complex.

Thanks !

New→Needs Votes
Terms & ConditionsCookie settings