---
title: "Dev Mode"
description: "Reference for the dev-mode.conf configuration file."
stack: "Community Stack (open source) — version 0.21.0"
stack_version: "0.21.0"
stack_comparison: https://docs.walt.id/community-vs-enterprise.md
canonical_url: https://docs.walt.id/community-stack/issuer2/configurations/config-files/dev-mode
generated: 2026-07-20
---
# Dev Mode Configuration

The `dev-mode.conf` file holds development-only settings. In the issuer it currently exposes a single option: whether `did:web` resolution may use plain HTTP instead of HTTPS only.

## File Location

```
waltid-services/waltid-issuer-api2/config/dev-mode.conf
```

## Enabling It

`dev-mode.conf` is only read when the `dev-mode` feature is enabled in `_features.conf`:

```hocon
# _features.conf
enabledFeatures = ["dev-mode"]
```

```hocon
# dev-mode.conf
enableDidWebResolverHttps = false
```

If the feature is enabled but `dev-mode.conf` can't be loaded, the issuer logs a warning and keeps the secure default.

## `enableDidWebResolverHttps`

| Value | Effect |
|-------|--------|
| `true` (default) | `did:web` documents are fetched over **HTTPS** only |
| `false` | `did:web` documents may be fetched over **HTTP** |

`did:web` resolves a DID by fetching a document over the network — e.g. `did:web:localhost:7002` → `http://localhost:7002/.well-known/did.json`. Local services usually run without TLS, so HTTP resolution must be allowed to use `did:web:localhost`. This is the only behaviour the `dev-mode` feature affects in the issuer; enabling the feature without setting this to `false` changes nothing.

## Related Configuration

- [Features](https://docs.walt.id/community-stack/issuer2/configurations/config-files/features.md) – Enable/disable features
- [Issuer Service](https://docs.walt.id/community-stack/issuer2/configurations/config-files/issuer-service.md) – Configure issuer DID