There is no issue wth having two (or more) interfaces in the same net/subnet, as long as they have different host addresses.
You don't need to disable forwarding, routers will not route to the same net/subnet.
If the interfaces are not teamed (i.e., left at the default functionality, not "joined" for bandwidth multiplication or redundancy) then one will handle most (if not all) of the outbound traffic, and inbound traffic can be aimed at a specific interface.
For example, int1 @ 192.168.1.1 and int2 @ 192.168.1.2.
Int1 would be used as the general I/O.
Int2 could be used as the address of a web service, with the web service configured / bound to only that interface.
The drawback to this kind of configuration relates to security issues. Having an interface to the outside *and* and interface to the inside without some sort of firewall process and a buttload of filters and blocks enabled can provide an easy access for hackers. Exploits still pop up now and then for even the most locked-down web servers.
If your intention is to team the interfaces for bandwidth or redundancy, you will also need a switch configurable for the compatible protocol (like spanning tree or Etherchannel/LACP).
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...