Mixing internal and non-internal extractor results in internal extractor not working

[mwulftange]

When an internal extractor is used with a non-internal extractor, the internal extractor no longer appears to find a match and can no longer be referenced in a subsequent request.

Consider the following template:

id: internal-non-internal-extractor-test
info:
  name: Internal with non-internal extractor test
  description: >
    This template tests the behavior of an internal when combined with a
    non-internal extractor. To be targeted at <https://www.iana.org/>.
  author: unknown
  severity: unknown

http:
  - raw:
      - |
        GET {{BaseURL}} HTTP/1.1
      - |
        GET {{absolutePath}} HTTP/1.1

    req-condition: true
    extractors:
      - type: regex
        internal: true
        part: body_1
        name: absolutePath
        regex:
          - '<a href="(/domains)">'
        group: 1
      - type: regex
        internal: false
        part: body_2
        name: title
        regex:
          - '<title[^>]*>([^<]+)</title>'
        group: 1
    matchers:
      - type: regex
        part: body_2
        regex:
          - '<title[^>]*>([^<]+)</title>'

Nuclei version:

v3.1.10

Current Behavior:

Nuclei 3.1.4 and later with -debug return the following:

[WRN] [example] Could not make http request for https://www.iana.org/: unresolved variables found: absolutePath

Expected Behavior:

Nuclei 3.1.3 and 2.9.15 return the following:

[example:title] [http] [unknown] https://www.iana.org/domains [Domain Name Services]

Steps To Reproduce:

Run the template above against https://www.iana.org/:

nuclei -t internal-non-internal-extractor-test.yaml -u https://www.iana.org/